From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: undefined reference to `raise' with musl static toolchain
Date: Tue, 8 May 2018 12:34:23 -0400 [thread overview]
Message-ID: <20180508163423.GM1392@brightrain.aerifal.cx> (raw)
In-Reply-To: <20180508162226.GA30163@voyager>
On Tue, May 08, 2018 at 06:22:27PM +0200, Markus Wichmann wrote:
> On Tue, May 08, 2018 at 02:44:17PM +0200, Thomas Petazzoni wrote:
> > /home/thomas/projets/buildroot/output/host/lib/gcc/arm-buildroot-linux-musleabihf/6.4.0/libgcc.a(_dvmd_lnx.o): In function `__aeabi_idiv0':
> > /home/thomas/projets/buildroot/output/build/host-gcc-final-6.4.0/build/arm-buildroot-linux-musleabihf/libgcc/../../../libgcc/config/arm/lib1funcs.S:1354: undefined reference to `raise'
> [...]
> >
> > Does that ring any bell ?
> >
>
> It would appear that your version of libgcc references libc. Now, with
> static linking, the libraries must appear in the correct order to
> satisfy all dependencies, but here you have a circular dependency between
> libgcc and libc. Since all gcc compiled code depends on libgcc, and libc
> is compiled with gcc, there are only two ways to break the cycle:
>
> 1. Remove the dependency. No idea how, not unless you basically inline
> raise() into __aeabi_idiv0().
>
> 2. Add libc again after the command line.
gcc already does this if you pass -static. I suspect the issue is that
Thomas is using a toolchain where gcc doesn't know it's
static-linking, and ld only static-links because there's no libc.so
present. This setup is highly fragile and afaik it's not intended by
the gcc developers to work. I don't know if there's anything like
--enable-default-static for gcc but that would be the right solution
for a static-only toolchain I think.
Rich
next prev parent reply other threads:[~2018-05-08 16:34 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 [this message]
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
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=20180508163423.GM1392@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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).