From: "H. J. Lu" <hjl@lucon.org>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] <bits/string2.h> changes for GCC 3.2+ and 3.4+
Date: Thu, 27 May 2004 09:26:00 -0000 [thread overview]
Message-ID: <20040527010102.GA8045@lucon.org> (raw)
In-Reply-To: <20040526203623.GA3779@lucon.org>
On Wed, May 26, 2004 at 01:36:23PM -0700, H. J. Lu wrote:
> On Wed, May 26, 2004 at 10:26:26AM -0700, Ulrich Drepper wrote:
> > Applied.
> >
I think the patch is incomplete.
2004-05-26 Jakub Jelinek <jakub@redhat.com>
* include/string.h (mempcpy, stpcpy): Add libc_hidden_builtin_proto.
Don't you need to add the corresponding libc_hidden_builtin_def for
mempcpy and stpcpy? ld.so failed to build with gcc 3.4 on ia64 and
i686 due to missing mempcpy and stpcpy.
H.J.
next prev parent reply other threads:[~2004-05-27 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 17:27 Jakub Jelinek
2004-05-26 20:36 ` Ulrich Drepper
2004-05-27 1:01 ` H. J. Lu
2004-05-27 9:26 ` H. J. Lu [this message]
2004-05-27 9:47 ` [PATCH] <bits/string2.h> changes for GCC 3.2+ and 3.4+ (followup) Jakub Jelinek
2004-05-28 6:40 ` H. J. Lu
2004-05-28 6:42 ` Ulrich Drepper
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=20040527010102.GA8045@lucon.org \
--to=hjl@lucon.org \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.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).