Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 7 Oct 2014 17:32:12 -0400
From: stephen Turner <stephen.n.turner@...il.com>
To: musl@...ts.openwall.com
Subject: Re: libgcc errors

/root/code/gcc-build/./gcc/as: 106: exec: --32: not found

I have a directory /root/code/ for all my programs to be compiled. the
directory root/code/gcc-build is separate from the root/code/gcc source
directory as they recommended a separate folder to compile in.  knowing
this, wouldn't the link above reference an "as" program that was recently
compiled as a part of the gcc make process since its in the previously
empty gcc-build directory? If not then while using the --with-sysroot flag
would it pull a copy of it from this directory or the host system?

I'm also confused why this happens when i define --host or --target but not
when i drop those ./configure options? If i had a issue with "as" wouldn't
it create a similar error when compiling for a native glibc system?

By my understanding the first stage toolchain is debian's since you would
be referencing the toolchain used to attempt to compile this package
correct? Which would be the same tool chain used before
to successfully compile a gcc-4.6.4 which could static link but not dynamic
due to the lack of --host --target use as i was advised.

I apologize for my lack of experience with building toolchains. if there is
a known good tutorial for this i will gladly ref it however the best i have
found is lfs embedded which i am currently using (and not working).

Thanks for your time and assistance.

On Tue, Oct 7, 2014 at 3:51 PM, Szabolcs Nagy <nsz@...t70.net> wrote:

> * stephen Turner <stephen.n.turner@...il.com> [2014-10-07 14:54:33 -0400]:
> > configure:3362: /root/code/gcc-build/./gcc/xgcc
> > -B/root/code/gcc-build/./gcc/ -B/root/targetfs/i686-linux-musl/bin/
> > -B/root/targetfs/i686-linux-musl/lib/ -isystem
> > /root/targetfs/i686-linux-musl/include -isystem
> > /root/targetfs/i686-linux-musl/sys-include    -v >&5
> > Reading specs from /root/code/gcc-build/./gcc/specs
> > COLLECT_GCC=/root/code/gcc-build/./gcc/xgcc
> > COLLECT_LTO_WRAPPER=/root/code/gcc-build/./gcc/lto-wrapper
> > Target: i686-linux-musl
> > Configured with: ../gcc/configure --prefix=/root/targetfs
> > --enable-languages=c --disable-bootstrap --disable-multilib
> > --disable-shared --disable-nls --disable-mudflap --disable-libmudflap
> > --disable-libssp --disable-libgomp --with-newlib --without-headers
> > --target=i686-linux-musl --with-sysroot=/root/targetfs/
> > Thread model: posix
> > gcc version 4.9.0 (GCC)
> > configure:3373: $? = 0
> > configure:3362: /root/code/gcc-build/./gcc/xgcc
> > -B/root/code/gcc-build/./gcc/ -B/root/targetfs/i686-linux-musl/bin/
> > -B/root/targetfs/i686-linux-musl/lib/ -isystem
> > /root/targetfs/i686-linux-musl/include -isystem
> > /root/targetfs/i686-linux-musl/sys-include    -V >&5
> > xgcc: error: unrecognized command line option '-V'
> > xgcc: fatal error: no input files
> > compilation terminated.
> > configure:3373: $? = 1
> > configure:3362: /root/code/gcc-build/./gcc/xgcc
> > -B/root/code/gcc-build/./gcc/ -B/root/targetfs/i686-linux-musl/bin/
> > -B/root/targetfs/i686-linux-musl/lib/ -isystem
> > /root/targetfs/i686-linux-musl/include -isystem
> > /root/targetfs/i686-linux-musl/sys-include    -qversion >&5
> > xgcc: error: unrecognized command line option '-qversion'
> > xgcc: fatal error: no input files
> > compilation terminated.
> > configure:3373: $? = 1
> > configure:3389: /root/code/gcc-build/./gcc/xgcc
> > -B/root/code/gcc-build/./gcc/ -B/root/targetfs/i686-linux-musl/bin/
> > -B/root/targetfs/i686-linux-musl/lib/ -isystem
> > /root/targetfs/i686-linux-musl/include -isystem
> > /root/targetfs/i686-linux-musl/sys-include    -o conftest -g -O2
> > conftest.c  >&5
> > /root/code/gcc-build/./gcc/as: 106: exec: --32: not found
> > configure:3392: $? = 1
>
> your as does not accept --32 for some reason
> or it is called incorrectly in some way
>
> so the first stage toolchain is broken
>
> > configure:3580: checking for suffix of object files
> > configure:3602: /root/code/gcc-build/./gcc/xgcc
> > -B/root/code/gcc-build/./gcc/ -B/root/targetfs/i686-linux-musl/bin/
> > -B/root/targetfs/i686-linux-musl/lib/ -isystem
> > /root/targetfs/i686-linux-musl/include -isystem
> > /root/targetfs/i686-linux-musl/sys-include    -c -g -O2  conftest.c >&5
> > /root/code/gcc-build/./gcc/as: 106: exec: --32: not found
> > configure:3606: $? = 1
> > configure: failed program was:
> > | /* confdefs.h */
> > | #define PACKAGE_NAME "GNU C Runtime Library"
> > | #define PACKAGE_TARNAME "libgcc"
> > | #define PACKAGE_VERSION "1.0"
> > | #define PACKAGE_STRING "GNU C Runtime Library 1.0"
> > | #define PACKAGE_BUGREPORT ""
> > | #define PACKAGE_URL "http://www.gnu.org/software/libgcc/"
> > | /* end confdefs.h.  */
> > |
> > | int
> > | main ()
> > | {
> > |
> > |   ;
> > |   return 0;
> > | }
> > configure:3620: error: in `/root/code/gcc-build/i686-linux-musl/libgcc':
> > configure:3623: error: cannot compute suffix of object files: cannot
> compile
> > See `config.log' for more details.
>

Content of type "text/html" skipped

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.