Frederick Karl Kepner DuPuy wrote:
Secondly, as you can see from my second email, I took the advice of Adriaan van Os and rolled back my assembler/linker to version 590.36. (They had previously been v. 622.5.) But what you write has gotten me worried: although this solved my present gpc compiling problem, have I messed with the Xcode suite in a way I shouldn't have-- one which could come back and bite me in the future should I ever begin to use it properly? (Right now command-line gpc is all I do; but who knows what the future might hold!) Was I irresponsible?
There is little reason to worry. You can always reinstall Xcode later, which will reinstall cctools-622.5 (or whatever version Apple includes). Besides, the solution I proposed is a temporary one. As soon as I have a little time, I will look at providing a new compiler build. But of course, you can also use the compiler built by Gale Paeper, as outlined in his previous post.
Waldek Hebisch wrote some time ago
I will probably release a new snapshot shortly after gcc-4.1.2 is released. Concerning labels like beta or "release": these labels mark confidence that quality goals are met. _Every_ snapshot is expected to work well in simple cases. So the main quality indicator is how well the snapshot work in unusual situations: on some rare machines, on some strange programming constucts. Also, it matter if many little details (like warnings ...) are handled as expected.
Gpc quality standard is high, basically we would like that the compiler works correctly in _all_ aspects. ATM there is a few long standing problems (most not related to 4.1 port) which I feel that should be fixed in "release" version. Some were fixed in previous snapshots, but it will take some time to fix them all.
It would be really great if the last remaining gcc-4 problems are solved. Continuous OS evolvement ties us to the latest gcc versions.
Regards,
Adriaan van Os