From: Rob Landley <rob@landley.net>
To: musl@lists.openwall.com
Subject: Re: Re: libgcc --disable-shared test case
Date: Sat, 11 Jan 2014 20:35:50 -0600 [thread overview]
Message-ID: <52D1FF86.80800@landley.net> (raw)
In-Reply-To: <52D1D9DF.1010300@barfooze.de>
On 01/11/14 17:55, John Spencer wrote:
> Rich Felker wrote:
>> 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
In 4.2 there is no libgcc/Makefile.in, instead there's a mklibgcc.in
generating the file. Given that it's generating a value and assigning it
to vis_hide a few lines earlier, I have no idea if the suggested fix
(trying to pass through a value from autoconf?) is relevant to this
version of the code.
The real problem is I have no way to reproduce the failure yet. The
comment that it occurs building musl for mips seems useful, I'll try
that. But it's kinda hard to fix a failure I've never seen fail...
Rob
next prev parent reply other threads:[~2014-01-12 2:35 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
2014-01-12 2:35 ` Rob Landley [this message]
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=52D1FF86.80800@landley.net \
--to=rob@landley.net \
--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).