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] |
I have successfully compiled gcc 3.4 for a ppc970. The attached patch is very similar to the one I have send a few weeks ago. There are two significant changes:
1) add a "ln -s libgcc.a libgcc_s.a" (cvs libc thinks it needs it) ... +cd ${PREFIX}/lib/gcc/$TARGET/3.4.0/ +ln -s libgcc.a libgcc_eh.a +ln -s libgcc.a libgcc_s.a
That makes me nervous. I suspect gcc is not being compiled properly, and that we need to figure out how to get gcc to really build libgcc_{eh,s}.a!
2) use "--enable-kernel=2.6.5". This is necessary to compile with the headers from kernel 2.6.5
What do you thing about using a variable MIN_KERNEL as the parameter to --enable-kernel? I.e use --enable-kernel=$MIN_KERNEL.
By the way, what was it that made you not want to enable all the addons for glibc? I guess it was the nptl vs. linuxthreads choice? - Dan
-- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change
------ 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] |