[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180509152437.GY4418@port70.net>
Date: Wed, 9 May 2018 17:24:37 +0200
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Cc: Rich Felker <dalias@...c.org>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>
Subject: Re: undefined reference to `raise' with musl static toolchain
* Thomas Petazzoni <thomas.petazzoni@...tlin.com> [2018-05-09 15:44:07 +0200]:
>
> So: why does a musl-based toolchain requires an explicit -static, while
> it isn't needed with uClibc-ng ?
>
there can be many reasons..
e.g. if mktime in uclibc-ng happens to reference raise then it
would get linked in independently of libgcc.
or maybe uclibc-ng has its own __aeabi_*div implementation.
or the way libgcc was configured, the raise(SIGFPE) was disabled
(it is only enabled for linux targets, but who knows how
*-linux-uclibcgnueabihf is interpreted).
you can check these using nm/objdump/readelf on libc.a and libgcc.a
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.
