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 was trying to compile busybox 0.60-5 statically for ppc405 & ppc750 using the tool-chain that we just built (gcc 3.3.3, glibc 2.3.2, binutils 2.15, linux kernel 2.6.6). busybox builds fine statically for ppc750 but not for ppc405. I can build a dynamically linked version for ppc405 and it runs fine on the target. I won't be running the statically linked version of busybox on my targets but it would be nice to know why it doesn't compile. I wrote a simple shell script which I use to create the problem. I've attached the shell script, busybox configuration file and the result of running the shell script for 4 different cases (ppc405|ppc750 X dyanmic|static). Could this be a problem in our tool-chain? ankur ps. hello.c & hello2.cc (part of the cross-tool distribution) did compile fine statically & dynamically for ppc405 & ppc750.
Attachment:
script-results.txt
Description: Text document
Attachment:
Config.h
Description: Binary data
Attachment:
static-compile-test.sh
Description: Binary data
------ 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] |