[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120920175253.GW9428@port70.net>
Date: Thu, 20 Sep 2012 19:52:53 +0200
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Subject: Re: musl-gcc question
* Jens <jensl@...s.mine.nu> [2012-09-20 16:50:13 +0200]:
> bash-4.1# musl-gcc -v -o m -static t.c
> Invoked as gcc
> Reference path: /bin/..
> arg[ 0] = rawgcc
> arg[ 1] = -nostdlib
> arg[ 2] = -static
> arg[ 3] = -Wl,-rpath-link,/bin/../lib
> arg[ 4] = -L/bin/../lib
> arg[ 5] = -L/bin/../gcc/lib
> arg[ 6] = -nostdinc
> arg[ 7] = -isystem
> arg[ 8] = /bin/../include
> arg[ 9] = -isystem
> arg[10] = /bin/../gcc/include
> arg[11] = -U__nptl__
> arg[12] = /bin/../lib/crti.o
> arg[13] = /bin/../gcc/lib/crtbeginT.o
> arg[14] = /bin/../lib/crt1.o
> arg[15] = -v
> arg[16] = -o
> arg[17] = m
> arg[18] = -static
> arg[19] = t.c
> arg[20] = -specs
> arg[21] = /opt/musl/lib/musl-gcc.specs
> arg[22] = -lgcc
> arg[23] = -lgcc_eh
> arg[24] = -lc
> arg[25] = -lgcc
> arg[26] = -lgcc_eh
> arg[27] = /bin/../gcc/lib/crtend.o
> arg[28] = /bin/../lib/crtn.o
now i see that gcc calls some rawgcc with extra arguments here
that may be a problem for musl-gcc
the spec file cant help if gcc already adds -nostdlib and -nostdinc
(then you already asked for a freestanding environment)
call rawgcc directly from musl-gcc
i think that should work
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.
