public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "drepper at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/1054] regex_internal.h redefines __mempcpy when used outside libc
Date: Thu, 22 Sep 2005 18:39:00 -0000 [thread overview]
Message-ID: <20050922183937.6862.qmail@sourceware.org> (raw)
In-Reply-To: <20050707082832.1054.eggert@gnu.org>
------- Additional Comments From drepper at redhat dot com 2005-09-22 18:39 -------
> Uli, it's glibc that defines __mempcpy as part of the string inlines
> stuff. It's not an unsupported platform, it's just
> --with-included-regex on a glibc system.
What are you talking about? The patch is not needed for compiling glibc.
Period. Therefore any such horrible workaround does not belong in glibc. All
this configuration handling which is of no interest to glibc should be kept
elsewhere which is what I said in my comment.
Either send a patch which moves all this nonsense into a separate file (which is
not part of glibc) or live with the current code.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=1054
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2005-09-22 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 8:28 [Bug regex/1054] New: " eggert at gnu dot org
2005-07-07 8:30 ` [Bug regex/1054] " eggert at gnu dot org
2005-09-06 16:35 ` drepper at redhat dot com
2005-09-06 16:49 ` paolo dot bonzini at lu dot unisi dot ch
2005-09-22 18:39 ` drepper at redhat dot com [this message]
2006-04-25 18:17 ` drepper at redhat dot com
2006-08-24 6:54 ` drepper at redhat dot com
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=20050922183937.6862.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs-regex@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).