------- Comment #29 from danp57 at optonline dot net 2010-04-16 17:06 ------- Subject: Re: gcc 4.5 20100218 bootstrap compare fails on os x 10.6
I have one more comment to add. Perusing the log file, I noticed that it was not building what I expected. I was not looking for -m32's. I re-ran configure with configure ABI=64 --enable-languages=c,c++,objc,obj-c++,fortran and the code built correctly! I am aware that the sort of dual-personality 32bit/64bit character of Apple Leopards is a pain - but it strikes me that the configure is generating something that the rest of the build struggles with... why is this showing up in gomp? Best, Dan On Apr 16, 2010, at 10:34 AM, dominiq at lps dot ens dot fr wrote: > > > ------- Comment #26 from dominiq at lps dot ens dot fr 2010-04-16 14:34 > ------- > First a Note for Ralf Wildenhues: I have seen somewhere that libgomp have been > added to stage2 starting from some revision, but I am unable to find where. Do > you have a better memory? > I think it is after 4.4 (so nothing can be infered from building 4.4.x). > >> In this case, I have found the bug consistently repeatable on multiple >> machines, all running snow leopard up-to-date. When built on my desk-top >> machine there were no other applications running except for "TeamViewer" (I >> built it from work). The other builds were made without TeamViewer. >> Browsers >> on/off, doesn't matter. > > Can you > > (1) check that your builds fail as reported in comment #13 (you have to check > stageX-x86_64-apple-darwin10/YYY/libgomp/config.log with X in 2 or 3 and YYY > in > . or i386 assuming you build for x86_64-apple-darwin10)? > > (2) provide your full configure line? > >> I *have* a build that works -- I built it with gcc-4.4.3 with no problem. >> The >> difficulty is with Apple's gcc distribution. As I pointed out earlier, I'd >> be >> struggling if I didn't have a new version of gcc on-board. The only thing I >> did not try is to see if I used a gcc-4.5.0 build with --disable-bootstrap >> from >> Apple's gcc to rebuild gcc-4.5.0 with itself... Even then, I'd be somewhat >> worried that the then consistent compiler might be producing code at variance >> with builds on other operating systems yielding inexplicable bugs or bugs >> that >> other people could not reproduce on their platforms. > > In my builds stage1 use Apple stock gcc: gcc version 4.2.1 (Apple Inc. build > 5659). > The only way I know that can convince anybody that the build is sane is to run > make check for 32 and 64 bit modes (though it's certainly not a proof!-). > > > -- > > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43170 > > ------- You are receiving this mail because: ------- > You are on the CC list for the bug, or are watching someone who is. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43170
