From: Zack Weinberg <zackw@panix.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Andreas Schwab <schwab@suse.de>,
GNU C Library <libc-alpha@sourceware.org>,
Siddhesh Poyarekar <siddhesh@gotplt.org>
Subject: Re: Evolution of ELF symbol management
Date: Tue, 22 Nov 2016 15:48:00 -0000 [thread overview]
Message-ID: <CAKCAbMg0iTwH0NQydmdy9e7wWyprQEb0DjPvGh2pjcirzCSmaw@mail.gmail.com> (raw)
In-Reply-To: <543ff4e2-48da-43d4-7688-6973baeaec9f@redhat.com>
On Tue, Nov 22, 2016 at 10:39 AM, Florian Weimer <fweimer@redhat.com> wrote:
> On 11/22/2016 04:29 PM, Andreas Schwab wrote:
>>
>> On Nov 22 2016, Florian Weimer <fweimer@redhat.com> wrote:
>>
>>> There also configure scripts which do
>>>
>>> extern char whatever();
>>> main () { whatever(); }
>>>
>>> for link testing, without including the appropriate header (perhaps
>>> deliberately). That could be considered broken. I'm not sure.
>>
>> While getting the return type wrong makes it slightly broken, the C
>> standard does support declaring standard functions on your own, as long
>> as you don't need special types.
>
> Yes, that's true. Thanks for the reminder.
As a practical matter, also, Autoconf has done this for decades and no
one has even sketched a design for a replacement; I think we must
assume we will need to support it for the foreseeable future.
zw
next prev parent reply other threads:[~2016-11-22 15:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 9:26 Florian Weimer
2016-10-18 16:50 ` Joseph Myers
2016-10-25 14:32 ` Florian Weimer
2016-10-25 15:37 ` Joseph Myers
2016-11-21 15:35 ` Florian Weimer
2016-10-26 12:17 ` Joseph Myers
2016-11-20 11:13 ` Mike Frysinger
2016-11-21 10:12 ` Florian Weimer
2016-11-16 15:55 ` Zack Weinberg
2016-11-18 15:48 ` Florian Weimer
2016-11-19 17:25 ` Zack Weinberg
2016-11-22 15:09 ` Florian Weimer
2016-11-22 15:30 ` Andreas Schwab
2016-11-22 15:39 ` Florian Weimer
2016-11-22 15:48 ` Zack Weinberg [this message]
2016-11-22 15:48 ` Zack Weinberg
2016-11-22 17:42 ` Joseph Myers
2016-11-23 14:09 ` Zack Weinberg
2016-11-24 10:01 ` Florian Weimer
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=CAKCAbMg0iTwH0NQydmdy9e7wWyprQEb0DjPvGh2pjcirzCSmaw@mail.gmail.com \
--to=zackw@panix.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
--cc=siddhesh@gotplt.org \
/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).