Re: Am I crazy? Does newlib build nothing? SOLVED

[Bryan Ischo <bryan at ischo dot com>]

On 08/04/11 15:06, Bryan Ischo wrote:
> make[6]: Entering directory 
> `/tmp/foo/i686-unknown-linux-gnu/newlib/libc/machine/i386'
> cc     -DPACKAGE_NAME=\"newlib\" -DPACKAGE_TARNAME=\"newlib\" 
> -DPACKAGE_VERSION=\"1.19.0\" -DPACKAGE_STRING=\"newlib\ 1.19.0\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -I. 
> -I/home/bji/buildtools/newlib-1.19.0/newlib/libc/machine/i386 -I 
> /home/bji/buildtools/newlib-1.19.0/newlib/libc/machine/i386/../../../libm/common 
> -DMISSING_SYSCALL_NAMES -fno-builtin     -I 
> /home/bji/buildtools/newlib-1.19.0/newlib/libc/machine/i386/../../../libm/common 
> -DMISSING_SYSCALL_NAMES -fno-builtin   -g -O2 -c -o lib_a-memchr.o 
> `test -f 'memchr.S' || echo 
> '/home/bji/buildtools/newlib-1.19.0/newlib/libc/machine/i386/'`memchr.S
> /home/bji/buildtools/newlib-1.19.0/newlib/libc/machine/i386/memchr.S: 
> Assembler messages:
> /home/bji/buildtools/newlib-1.19.0/newlib/libc/machine/i386/memchr.S:17: 
> Error: invalid instruction suffix for `push'
> /home/bji/buildtools/newlib-1.19.0/newlib/libc/machine/i386/memchr.S:19: 
> Error: invalid instruction suffix for `push'
> /home/bji/buildtools/newlib-1.19.0/newlib/libc/machine/i386/memchr.S:69: 
> Error: invalid instruction suffix for `push'
> /home/bji/buildtools/newlib-1.19.0/newlib/libc/machine/i386/memchr.S:87: 
> Error: invalid instruction suffix for `pop'
> /home/bji/buildtools/newlib-1.19.0/newlib/libc/machine/i386/memchr.S:112: 
> Error: invalid instruction suffix for `pop'
> make[6]: *** [lib_a-memchr.o] Error 1

This turned out to be due to me using an x86_64 targeting compiler when 
trying to build newlib; you have to use an i686 targeting compiler.  
This was mentioned previously in a different response in this thread.  
This turns out not to be an issue for me because my cross-compilation 
environment is using an i686 "bootstrapping" minimal compiler when 
compiling newlib; the error I reported above only happened when I was 
testing my solution to getting newlib to build ("--with-newlib 
--host=i686-unknown-linux-gnu") using a non-cross-compiling environment.

Thanks,
Bryan