This is a tracker bug for all errors one can get when trying to build Firefox with Apple's gcc-3.5-tree-ssa additional information about my compiler: Reading specs from /usr/lib/gcc/powerpc-apple-darwin/3.5.0-tree-ssa/specs Configured with: /Volumes/FW_Jaguar/TEMP/Builds/GCC/gcc-1765/build/obj/src/configure --disable-checking --prefix=/usr --disable-libmudflap --mandir=/share/man --enable-languages=c,objc,c++ --disable-libada --program-transform-name=/^[cg][^+.-]*$/s/$/-3.5/ --with-gxx-include-dir=/include/gcc/darwin/3.5/c++ --build=powerpc-apple-darwin --host=powerpc-apple-darwin --target=powerpc-apple-darwin Thread model: posix gcc version 3.5.0-tree-ssa 20040321 (merged 20040529) (Apple Computer, Inc. build 1765)
Additional information about Apple gcc-3.5-tree-ssa: This compilier will be included in MacOS X 10.4, it might even be avaliable as an update for OSX 10.3 and less *before* 10.4 is released. So we might want to get all the issues resolved *before* lots of people try to compile with this compiler.
CCing jst and dbaron
Help wanted to fix all the bugs blocking this one! CCing pinkerton, he might be able to help, too.
Note: all "invalid conversions" can be worked around with the gcc-flag "-fpermissive" (at least in OS X.3.5 on a G4). This does *not*, however, work around bug 257108. But as some of the datatypes might cause problems on 64bit machines, we should not use this workaround.
I think that this is probably invalid, along with everything that it's dependent on. We now build with Apple's shipping 4.0 compiler (their second attempt as released with Xcode 2.1, their first attempt in 2.0 had bugs). In Apple-land, 3.4 and 3.5 were mere stops along the developmental continuum. Of everything here, anything that's an actual bug of ours has probably already been FIXED already, others are most likely INVALID. Martin, if anything here still presents a problem for you, please make a note. Otherwise, these can just be closed out.
IIRC, any 3.5-generation compiler from Apple was at best a preview for developers at WWDC and the like; it's no longer a part of the Tiger SDK for example, and definitely not supported by Apple. Who gets to close bugs?
In the absence of any response, I take it upon myself to clean up the bug db.