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] |
Hi Mohammed, >I write the following commands: > >1) ln -s /usr/local/lib/gcc-lib/powerpc-unknown-eabi/ >./powerpc-unknown-eabi/ > >2) /usr/local/bin/powerpc-unknown-eabi-gcc.exe -b >powerpc-unknown-eabi -o test -mcpu=860 test.c 1) Where did you use this command? 2) you do either : "gcc -b powerpc-unknown-eabi -mcpu=860 -o test test.c" OR "powerpc-unknown-eabi -mcpu=860 -o test test.c" Not a mix of both. The first lets the native GCC invoke the powerpc tools, while the second calls it directly. >But still I get the same error as before i.e. > That's because you are working for an embedded target. The 'target' does not know anything about what you want. (i.e. what adres should the code go, or what are the interrupt vectors.) You got to teach it. I suggest reading up on "linker scripts" and how to make one. (try "info ld" on the command line) And also the mailing list archives. Best Regards, jan ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |