Frank Jahnke wrote:
GPC. (The internals changed in GCC, and GPC will have to adjust. Since this seems to mean an integrated preprocessor, this won't be a small fix, and might take some time. There's only a quick work-around for now, but as I said, unless there's a good reason to use gcc-3.3.x, it might be better to avoid it with GPC for now.)
OK. 3.2.3_1 is in the FreeBSD ports tree (and nine others of various vintages). Let me try that one.
This has no effect on linking the different compilers? That is counterintuitive...
I'm not sure I understand what you mean. Do you mean that different GCC versions *need* to be imcompatible? ;-) Anyway, I have not much experience under FreeBSD. On Linux, DJGPP and Solaris I haven't had such problems even with widerly varying versions (we once did, some years ago, under Solaris, gcc-2.8.x for gpc, gcc-2.95.x for g++ and some other version, perhaps even non-GNU C compiler, for C libraries used by both the Pascal and C++ parts and, perhaps somewhat surprisingly, it just worked) ...
Understood. Not an issue for the codes I want to use. I wrote these many, many years ago, and are simple optimization and finite difference and element codes for problems that are now again of interest. Rather than translate them to C, I thought it easier to get the Pascal compiler going. Yes, I tried p2c, but these are written in Berkeley Pascal, and hence non-standard enough that p2c choked.
If there are problems, they're most likely to show in system headers, which are used by the RTS.
That is good news. I have gmake; as long as documentation is available in other forms (for example, ps or pdf) then I would be good to go.
These formats are there on the homepage (beside HTML, of course). The info format is included with the non-minimal source distributions. Building any of them yourself requires GNU texinfo (and perhaps other tools, such as GNU awk and bash).
With all due respect, I find that info pages are not that useful. The man page -- yes. More information necessary? I go to paper manual.
To each their own. I find info files easier to use (given a good reader, of course; the default GNU info reader is quite awkward IMHO). But that's why I'm glad that we can build the different formats easily.
Frank