From: Andreas Schwab <schwab@linux-m68k.org>
To: Zack Weinberg <zackw@panix.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: ldbl_hidden_weak??
Date: Wed, 27 Dec 2017 08:38:00 -0000 [thread overview]
Message-ID: <m2k1x8lg4v.fsf@linux-m68k.org> (raw)
In-Reply-To: <CAKCAbMiKjowF-92Qwu_u9s0=WYS4Hf_qKhepzJB9QGCwn=_fxw@mail.gmail.com> (Zack Weinberg's message of "Tue, 26 Dec 2017 14:44:04 -0800")
On Dez 26 2017, Zack Weinberg <zackw@panix.com> wrote:
> The problem is what to put where it says /* ??? */. It can't be
> libc_hidden_weak (name), that gives me
>
> iovsprintf.c:50:93: error: ‘__EI_vsprintf’ aliased to undefined symbol
> ‘__GI_vsprintf’
> ldbl_hidden_weak (__IO_vsprintf, vsprintf)
I think that means you are missing a preceding ldbl_hidden_proto.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2017-12-27 8:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-26 22:44 ldbl_hidden_weak?? Zack Weinberg
2017-12-27 8:38 ` Andreas Schwab [this message]
2017-12-27 16:22 ` ldbl_hidden_weak?? Zack Weinberg
2017-12-27 21:46 ` ldbl_hidden_weak?? Andreas Schwab
2017-12-27 22:12 ` ldbl_hidden_weak?? 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=m2k1x8lg4v.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=libc-alpha@sourceware.org \
--cc=zackw@panix.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).