public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "paolo dot bonzini at lu dot unisi dot ch" <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: Tue, 06 Sep 2005 16:49:00 -0000	[thread overview]
Message-ID: <20050906164925.16740.qmail@sourceware.org> (raw)
In-Reply-To: <20050707082832.1054.eggert@gnu.org>


------- Additional Comments From paolo dot bonzini at lu dot unisi dot ch  2005-09-06 16:49 -------
Subject: Re:  regex_internal.h redefines __mempcpy when used
 outside libc

drepper at redhat dot com wrote:

>------- Additional Comments From drepper at redhat dot com  2005-09-06 16:35 -------
>This is all wrong.  I have no interest to waste my time on unsupported paltforms
>just because some people think supporting worthless platforms is useful.  If you
>want to do it, do it all by yourself.  I'm willing to accept a patch which
>removes all of those !_LIBC handling (especially in headers) as much as possible
>and add
>  
>
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.

Paolo


-- 


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.


  parent reply	other threads:[~2005-09-06 16:49 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 [this message]
2005-09-22 18:39 ` drepper at redhat dot com
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=20050906164925.16740.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).