From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: undefined reference to `raise' with musl static toolchain
Date: Wed, 9 May 2018 13:28:48 -0400 [thread overview]
Message-ID: <20180509172848.GN1392@brightrain.aerifal.cx> (raw)
In-Reply-To: <20180509152437.GY4418@port70.net>
On Wed, May 09, 2018 at 05:24:37PM +0200, Szabolcs Nagy wrote:
> * Thomas Petazzoni <thomas.petazzoni@bootlin.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
It would be nice if this raise dependency could be removed from
libgcc. It's not necessary for any defined behavior; it's only there
for the sake of emulating x86 behavior on div-by-zero.
Either way you need to be using the right link order that -static
gives (potentially for other reasons) but it would be nice to avoid
unnecessary code getting static-linked like this.
Rich
next prev parent reply other threads:[~2018-05-09 17:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 12:44 Thomas Petazzoni
2018-05-08 13:28 ` Alexander Monakov
2018-05-08 16:22 ` Markus Wichmann
2018-05-08 16:34 ` Rich Felker
2018-05-09 9:29 ` Thomas Petazzoni
2018-05-09 13:44 ` Thomas Petazzoni
2018-05-09 15:24 ` Szabolcs Nagy
2018-05-09 17:28 ` Rich Felker [this message]
2018-05-11 15:59 ` Thomas Petazzoni
2018-05-11 16:05 ` Rich Felker
2018-05-11 21:28 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180509172848.GN1392@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).