mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Szabolcs Nagy <nsz@port70.net>
Cc: musl@lists.openwall.com, Rich Felker <dalias@libc.org>
Subject: Re: undefined reference to `raise' with musl static toolchain
Date: Fri, 11 May 2018 17:59:01 +0200	[thread overview]
Message-ID: <20180511175901.7f17085a@windsurf.home> (raw)
In-Reply-To: <20180509152437.GY4418@port70.net>

Hello,

Thanks for your feedback.

On Wed, 9 May 2018 17:24:37 +0200, Szabolcs Nagy wrote:

> 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.

In the static binary linked against uClibc, there are two references to
__GI_raise:

	__GI_abort
	__aeabi_idiv0

__GI_abort is reference from _start, so I guess this means that
__GI_abort is always pulled in, therefore __GI_raise is always pulled
in, and __aeabi_idiv0 is happy.

Now my question remains: do you consider it normal that -static is
required, or do you consider it a bug of the musl/gcc integration that
-static is required even when the only variant available of the library
is the static one ?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com


  parent reply	other threads:[~2018-05-11 15:59 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
2018-05-11 15:59           ` Thomas Petazzoni [this message]
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=20180511175901.7f17085a@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    --cc=nsz@port70.net \
    /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).