From: John Spencer <maillist-musl@barfooze.de>
To: musl@lists.openwall.com
Subject: Re: Re: libgcc --disable-shared test case
Date: Sun, 12 Jan 2014 00:55:11 +0100 [thread overview]
Message-ID: <52D1D9DF.1010300@barfooze.de> (raw)
In-Reply-To: <20140111224509.GX24286@brightrain.aerifal.cx>
Rich Felker wrote:
> On Sat, Jan 11, 2014 at 04:38:36PM -0600, Rob Landley wrote:
>> On 01/11/14 16:23, Rich Felker wrote:
>>> On Sat, Jan 11, 2014 at 04:04:25PM -0600, Rob Landley wrote:
>>> If you want to see the issue manifest without replacing uclibc, the
>>> easiest way would be to check *which* libgcc symbols got pulled into
>>> libc.so.0, then modify the test code for libfoo.so to use a feature
>>> that will pull in one of the libgcc symbols not in libc.
>>>
>>> Rich
>> My goal is to make it work, with a brick if necessary. This includes
>> making it all work under musl.
>>
>> I'm already patching the libgcc.a build to produce libgcc_eh.a at
>> inappropriate times and shoehorning in symbols that problably
>> shouldn't go in there. (And then ccwrap is shoehorning in
>> libgcc_eh.a when it pulls in libgcc.a.)
>>
>> My position on the --disable-shared gcc being subtly broken is that
>> it's a bug in gcc I should fix (at least until replacing one more
>> FSF project with something better). Generally if I can reproduce a
>> problem and get enough time to work on it, I can fix it. I just
>> wanted to make sure that my failure to reproduce this issue wasn't
>> because I subtly screwed up. :)
>
> The way to fix it is to find the conditional logic in the gcc build
> system (I forget whether it's in configure, the Makefiles, or the
> headers) that disables use of the visibility attribute when
> --disable-shared is passed, and simply dummy it out so that visibility
> is always used. At one point we discussed on IRC how this could be
> fixed at the GCC level, so I could probably dig something out of IRC
> logs if you want.
that would be
https://github.com/sabotage-linux/sabotage/blob/36661440192e2ec51531ea81c7866578010f3283/KEEP/gcc-454-libgcc_hidden.patch
>
> Rich
>
next prev parent reply other threads:[~2014-01-11 23:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131017060913.GA1957@brightrain.aerifal.cx>
2014-01-11 17:40 ` Rob Landley
2014-01-11 21:51 ` Rich Felker
2014-01-11 22:04 ` Rob Landley
2014-01-11 22:23 ` Rich Felker
2014-01-11 22:38 ` Rob Landley
2014-01-11 22:45 ` Rich Felker
2014-01-11 23:10 ` Rob Landley
2014-01-11 23:55 ` John Spencer [this message]
2014-01-12 2:35 ` Rob Landley
2014-01-12 9:54 ` John Spencer
2014-01-12 15:33 ` 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=52D1D9DF.1010300@barfooze.de \
--to=maillist-musl@barfooze.de \
--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).