From: Rich Felker <dalias@libc.org>
To: u-igbb@aetey.se
Cc: musl@lists.openwall.com
Subject: Re: compiling musl on x86_64 linux with pcc
Date: Tue, 23 Sep 2014 15:31:34 -0400 [thread overview]
Message-ID: <20140923193134.GL23797@brightrain.aerifal.cx> (raw)
In-Reply-To: <20140923190525.GJ13475@example.net>
On Tue, Sep 23, 2014 at 09:05:25PM +0200, u-igbb@aetey.se wrote:
> On Mon, Aug 25, 2014 at 11:46:17AM -0400, Rich Felker wrote:
> > Note that some fixes are needed for
> > pcc-libs:
> >
> > - You need to remove the broken csu files and replace them with
> > symlinks to the musl files.
> >
> > - You need to add __attribute__((__visibility__("hidden"))) to all
> > external functions in libpcc.
> >
> > - You need to add -fPIC to the CFLAGS for building libpcc or you get a
> > broken libpcc (containing textrels) that can't be used for building
> > libc.so and that's harmful for use with any other shared libs.
>
> I followed these directions and musl with pcc play along very well for me
> (on i386).
>
> One strange thing I notice though, which is probably more pcc-related
> than musl (even though this concerns a musl-based toolchain).
>
> If I build a shared library with pcc without supplying -Wl,-Bsymbolic
> (or -Wl,-Bsymbolic-functions as musl does) then a(ny) binary linked to that
> library segfaults at start even if it does not actually need/use the
> library. I noticed this with libpcap and wonder what is the reason. Adding
> -Wl,-Bsymbolic makes everything work so the code is not exactly broken.
>
> Wonder if you happen to guess a possible reason for such kind of trouble,
> something that pcc gets wrong? This looks related to runtime linking
> behaviour so possibly not fully offtopic here.
Have you checked that this happens with all libs, or did you only
observe it with libpcap? If you have a minimal example .so file that
causes the crash when loaded, can you post it somewhere I could
download a copy to analyze, and also post the commands you used to
produce it?
Rich
next prev parent reply other threads:[~2014-09-23 19:31 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 9:18 compiling musl on x86_64 linux with ppc u-igbb
2014-08-13 9:29 ` "pcc" of course ([musl] compiling musl on x86_64 linux with ppc) u-igbb
2014-08-13 9:49 ` compiling musl on x86_64 linux with ppc Szabolcs Nagy
2014-08-13 10:25 ` compiling musl on x86_64 linux with pcc u-igbb
2014-08-13 11:22 ` u-igbb
2014-08-13 11:53 ` summary: [musl] " u-igbb
2014-08-13 12:38 ` compiling musl on x86_64 linux with ppc Rich Felker
2014-08-13 12:56 ` u-igbb
2014-08-13 14:23 ` Rich Felker
2014-08-13 14:43 ` compiling musl on x86_64 linux with pcc u-igbb
2014-08-13 14:43 ` compiling musl on x86_64 linux with ppc Szabolcs Nagy
2014-08-14 7:10 ` compiling musl on x86_64 linux with pcc u-igbb
2014-08-14 14:20 ` Rich Felker
2014-08-14 14:38 ` u-igbb
2014-08-14 14:47 ` Rich Felker
2014-08-14 15:00 ` u-igbb
2014-08-15 10:49 ` va_list (was: [musl] compiling musl on x86_64 linux with pcc) u-igbb
2014-08-15 13:44 ` Rich Felker
2014-08-15 15:07 ` u-igbb
2014-08-15 15:56 ` Rich Felker
2014-08-15 17:12 ` u-igbb
2014-08-15 8:05 ` compiling musl on x86_64 linux with ppc u-igbb
2014-08-25 8:28 ` compiling musl on x86_64 linux with pcc u-igbb
2014-08-25 8:34 ` u-igbb
2014-08-25 15:46 ` Rich Felker
2014-08-26 19:34 ` u-igbb
2014-08-26 19:54 ` Rich Felker
2014-08-27 7:40 ` u-igbb
2014-08-27 7:54 ` Rich Felker
2014-08-27 8:52 ` variadic args (was: [musl] compiling musl on x86_64 linux with pcc) u-igbb
2014-08-27 16:34 ` Rich Felker
2014-08-28 8:13 ` u-igbb
2014-08-28 14:40 ` Rich Felker
2014-08-28 16:55 ` u-igbb
2014-08-27 14:38 ` compiling musl with pcc (i486-pc-linux-gnu) " u-igbb
2014-08-27 16:36 ` Rich Felker
2014-09-23 19:05 ` compiling musl on x86_64 linux with pcc u-igbb
2014-09-23 19:31 ` Rich Felker [this message]
2014-09-24 8:26 ` u-igbb
2014-08-13 23:39 ` compiling musl on x86_64 linux with ppc Isaac Dunham
2014-08-13 23:41 ` Rich Felker
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=20140923193134.GL23797@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
--cc=u-igbb@aetey.se \
/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).