On Thursday 23 August 2007, James Ausmus wrote: > On 8/23/07, Mike Frysinger <[EMAIL PROTECTED]> wrote: > > On Wednesday 22 August 2007, James Ausmus wrote: > > > On 8/22/07, Mike Frysinger <[EMAIL PROTECTED]> wrote: > > > > On Wednesday 22 August 2007, James Ausmus wrote: > > > > > (As first seen on the gentoo-user mailing list, as I wasn't being > > > > > intelligent at the moment...) > > > > > > > > > > I am using the xmerge script as defined in > > > > > http://www.gentoo.org/proj/en/base/embedded/cross-development.xml, > > > > > all I get are either: > > > > > > > > > > /usr/libexec/gcc/arm-unknown-linux-gnueabi/ld: crt1.o: No such > > > > > file: No such file or directory > > > > > > > > keep it simple, leave configure scripts out of it > > > > > > > > start with a basic compile/link: > > > > $ echo 'int main(){}' > test.c > > > > $ arm-unknown-linux-gnueabi-gcc test.c > > > > > > Thanks for the response. :) > > > > > > Works fine, creates the a.out file, and file identifies it as: > > > > > > a.out: ELF 32-bit LSB executable, ARM, version 1 (SYSV), for GNU/Linux > > > 2.6.14, dynamically linked (uses shared libs), not stripped > > > > so now unpack a tarball by hand (something simple like sed-4.1.5.tar.gz) > > and test it out > > > > tar xf sed-4.1.5.tar.gz > > cd sed-4.1.5 > > ./configure --host=arm-unknown-linux-gnueabi > > Worked perfectly, as did the subsequent make all command... Sounds > like maybe something in portage itself that isn't working quite right > with cross-compilation? The resulting sed executable is in the same > format as the a.out previously generated with the arm- compiler...
then i'd snipe the config.log from the portage build dir, compress it, and post it to the list -mike
signature.asc
Description: This is a digitally signed message part.
