From: Geoff Keating <geoffk@geoffk.org>
To: Zack Weinberg <zack@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Darwin assert.h / shared libgcc mess
Date: Mon, 22 Nov 2004 22:50:00 -0000 [thread overview]
Message-ID: <97EC8AC0-3CD3-11D9-B3A6-000A95B1F520@geoffk.org> (raw)
In-Reply-To: <87fz3aptq4.fsf@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
On 15/11/2004, at 3:39 PM, Zack Weinberg wrote:
> Geoffrey Keating <geoffk@geoffk.org> writes:
>
>>> 2) Put __eprintf back into the shared libgcc, as an exported symbol,
>>> for all !inhibit_libc targets, so that fixincludes can rely on its
>>> being there. (If we instead use __assert, then __eprintf will
>>> remain a static-library-only backward compatibility symbol.)
>>
>> Is this really necessary? I'd rather have __eprintf linked into only
>> those apps that need it.
>
> Right now, any shared library that uses assert will fail to link.
> _Something_ has to be done. I'm open to alternative suggestions.
What I would do is put __eprintf in the static libgcc.a, and mark it as
hidden visibility so that it's private to each shared library.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2410 bytes --]
next prev parent reply other threads:[~2004-11-22 22:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 21:43 Zack Weinberg
2004-11-15 22:42 ` Geoffrey Keating
2004-11-16 3:49 ` Zack Weinberg
2004-11-22 22:50 ` Geoff Keating [this message]
2004-11-22 23:57 ` Zack Weinberg
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=97EC8AC0-3CD3-11D9-B3A6-000A95B1F520@geoffk.org \
--to=geoffk@geoffk.org \
--cc=gcc@gcc.gnu.org \
--cc=zack@codesourcery.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).