public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "eggert at gnu dot org" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs-regex@sources.redhat.com Subject: [Bug regex/1054] New: regex_internal.h redefines __mempcpy when used outside libc Date: Thu, 07 Jul 2005 08:28:00 -0000 [thread overview] Message-ID: <20050707082832.1054.eggert@gnu.org> (raw) I just now adapted coreutils to bundle the new regular expression implementation of libc instead of the old one that it was using. But I ran into a problem when I built this implementation under Debian GNU/Linux 3.1 r0a. The problem is that Debian's include files (which are from glibc) #define __mempcpy for efficiency, and this clashes with the #define in regex_internal.h. I will attach the patch I used to work around the problem; it uses an ifndef to avoid the redefinition. It might not hurt to put similar wrappers around the other symbols thus defined, I suppose. This patch is currently installed in gnulib, and I'm filing this bug report to have it propagated into libc proper. Thanks. -- Summary: regex_internal.h redefines __mempcpy when used outside libc Product: glibc Version: 2.3.5 Status: NEW Severity: normal Priority: P2 Component: regex AssignedTo: gotom at debian dot or dot jp ReportedBy: eggert at gnu dot org CC: glibc-bugs-regex at sources dot redhat dot com,glibc- bugs at sources dot redhat dot com GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://sources.redhat.com/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 reply other threads:[~2005-07-07 8:28 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-07-07 8:28 eggert at gnu dot org [this message] 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 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=20050707082832.1054.eggert@gnu.org \ --to=sourceware-bugzilla@sources.redhat.com \ --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: linkBe 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).