This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Gcc4 issues (was: CT 0.29 - stuck compiling gcc 4.0 glibc 2.2.5 ppc405: exec



FWIW, I'm running a complete development system built with the tools' CVS versions from begin december (glibc-2.3.4, gcc-4.0-experimental and binutils-2.15-cvs). Had to fix a number of packages, though, that used deprecated C-constructs...

(Any packages we would know about? Did you submit patches upstream?)

nothing big. I believe one (unfixed) was in dosbox (or libSDL). Most other packages were already fixed in CVS, but I had some trouble preparing the CVS versions for compilation (due to inexperience with the gnu automake/autoconf tools). I ended up fixing the latest releases, since that was easier for me.


And no, I have not yet sent a patch to the maintainers. But I agree that I should :)


It's i686, so primary target and as such will get the most testing, but so far I have only encountered one segfault (python 2.4 make check) and two ICEs, one during the build of X.org and one building Enlightenment DR17.

(and a double-free warning in mke3fs)

Not bad! Have they fixed the ICEs yet?

One is fixed, the other had a proposed fix which had some nasty side effects. I believe that one is still open. It made me feel bad about reporting it without being able to help fix it...


(it's http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20491)

Regards,
Arno

_________________________________________________________________
MSN Search, for accurate results! http://search.msn.nl


------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]