From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6891 invoked by alias); 22 Sep 2005 18:39:42 -0000 Mailing-List: contact glibc-bugs-regex-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-regex-owner@sources.redhat.com Received: (qmail 6863 invoked by uid 48); 22 Sep 2005 18:39:37 -0000 Date: Thu, 22 Sep 2005 18:39:00 -0000 Message-ID: <20050922183937.6862.qmail@sourceware.org> From: "drepper at redhat dot com" To: glibc-bugs-regex@sources.redhat.com In-Reply-To: <20050707082832.1054.eggert@gnu.org> References: <20050707082832.1054.eggert@gnu.org> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug regex/1054] regex_internal.h redefines __mempcpy when used outside libc X-Bugzilla-Reason: CC X-SW-Source: 2005-09/txt/msg00066.txt.bz2 List-Id: ------- 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.