This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug hurd/11638] regex.c fails to compile on Hurd
- From: "joseph at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Fri, 17 Feb 2012 13:08:42 +0000
- Subject: [Bug hurd/11638] regex.c fails to compile on Hurd
- Auto-submitted: auto-generated
- References: <bug-11638-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=11638
--- Comment #5 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2012-02-17 13:08:42 UTC ---
On Fri, 17 Feb 2012, tschwinge at sourceware dot org wrote:
> I hadn't realized these are imported/shared files. (Shouldn't this be
> mentioned somewhere prominently?) In this case, we'd go with the
I think gnulib's config/srclist.txt is the master list of files gnulib
gets from elsewhere, including those it gets from glibc. It's not perfect
- as I previously noted, gnulib's getcwd.c appears to be from glibc but
isn't listed there. And, various entries therein are commented out with
references to glibc bugs that are marked as FIXED - so whatever the
current reasons for those files not being fully in sync with glibc, the
lists of bugs in comments aren't particularly helpful.
I'd like to see these files more fully in sync between glibc and gnulib
again (as I said in
<http://sourceware.org/ml/libc-alpha/2012-01/msg00123.html>, the only
differences that seem essential are the gnulib changes to license headers
and gnulib's use of spaces instead of tabs for indentation, and those are
presumably handled automatically by the gnulib mechanism for updating from
external projects). But as noted in
<http://sourceware.org/ml/libc-alpha/2012-01/msg00129.html> and
<http://sourceware.org/ml/libc-alpha/2012-01/msg00128.html> this does
require gnulib maintainers to send lots of individual logical patches to
resync things.
For the shared files, it's generally glibc that is supposed to be the
master, not gnulib.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.