This is the mail archive of the crossgcc@sourceware.org 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: RE:Failure while building powerpc-unknown-linux-gnu


On Wednesday, July 21, 2010 5:31 PM, Peter Wippich wrote:


The strange thing is that I can build the toolchain for gcc 4.4.x, but this toolchain does not work for me. It compiles the kernel but user space stuff (busybox) is crashing at runtime when I use it.

Anybody has any hints what's going wrong here ??

I'm afraid I don't have any specific hints regarding a 4.3 version of gcc since for my 603e platform I am using 4.4.4, which after a couple of false starts has compiled and is running fine.


Are you using buildroot for your user space applications? There are some problems with it (at least there are in the 2010.05 version). In particular, in terms of sstrip and ldconfig.

First up, I'd recommend never to use sstrip: use the standard strip instead. I've found sstrip to be very broken on the 603e. I haven't checked the source code to sstrip, but I wouldn't be surprised if it is little-endian only!

Secondly, if you are using buildroot, then you need to remove the /etc/ld.so.cache file that it creates and create it again on your target hardware using the ldconfig compiled as part of crosstool. Also, when using buildroot, you might want to check that it does copy all the relevant libraries across from the crosstool build folder to the target directories. It already copies everything across to the buildroot staging folder, but some things get missed in the copy to the target folder structure.

Lastly, in terms of busybox, then there is a problem with strict aliasing, so you will need to set the -fno-strict-aliasing flag when compiling busybox (if you search the buildroot mailing list, someone posted about this some time back; the patch is at https://bugs.busybox.net/show_bug.cgi?id=1339). This one is quite deceptive, since it appears that gcc goes ahead with the optimisation even though it flags up a warning about it potentially breaking things.

Beyond that, you may find some "issues" compiling glibc/eglibc surrounding the FORTIFY_SOURCE option. Have a look at the config file I posted to this list some while back, since this may give you some ideas of some settings that may work - its available also at http://www.cygwin.com/ml/crossgcc/2010-07/msg00006.html.

I hope this gets you started... if you still have problems, let me know and I'll try to help further.

Cheers
Andy



--
For unsubscribe information see http://sourceware.org/lists.html#faq


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