public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug hurd/11638] regex.c fails to compile on Hurd
Date: Sun, 04 Nov 2012 14:40:00 -0000 [thread overview]
Message-ID: <bug-11638-131-XZCnT1r0H1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11638-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=11638
Thomas Schwinge <tschwinge at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #8 from Thomas Schwinge <tschwinge at sourceware dot org> 2012-11-04 14:39:51 UTC ---
Fixed as part of Roland's commit bea9b19322c77265033a068ac60c95a37e798a80
»Fix lots of bitrot for stub configurations.«:
[...]
* posix/regex.c: Include <sys/param.h> for MIN/MAX.
[...]
In NEWS marked as fixed in commit
512a49be20d42af59968513cd5094b3918cf6663.
Conciliating the different versions of this regex implementation (which
Paul said he is working on) is a different matter.
--
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.
next prev parent reply other threads:[~2012-11-04 14:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11638-131@http.sourceware.org/bugzilla/>
2012-02-17 8:16 ` eggert at gnu dot org
2012-02-17 8:17 ` eggert at gnu dot org
2012-02-17 9:22 ` tschwinge at sourceware dot org
2012-02-17 13:09 ` joseph at codesourcery dot com
2012-02-20 21:18 ` eggert at gnu dot org
2012-02-20 21:22 ` eggert at gnu dot org
2012-11-04 14:40 ` tschwinge at sourceware dot org [this message]
2014-06-30 17:55 ` fweimer at redhat dot com
2010-05-26 14:38 [Bug hurd/11638] New: " aurelien at aurel32 dot net
2010-05-26 14:39 ` [Bug hurd/11638] " aurelien at aurel32 dot net
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=bug-11638-131-XZCnT1r0H1@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).