public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/32263] Document the required versions of glibc and binutils
Date: Tue, 12 Jun 2007 04:34:00 -0000 [thread overview]
Message-ID: <20070612043428.1773.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32263-7959@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from pinskia at gcc dot gnu dot org 2007-06-12 04:34 -------
(In reply to comment #3)
> Well here's one example:
>
> http://foo-projects.org/pipermail/lunar-dev/2006-July/005821.html is the error
Actually that is a build failure with glibc. The real question is, does glibc
have requirements. GCC almost has no requirements on what maxium
glibc/binutils version it can be built with. glibc has some requirements
though.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32263
next prev parent reply other threads:[~2007-06-12 4:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 20:06 [Bug other/32263] New: " appfault at hotmail dot com
2007-06-08 20:16 ` [Bug other/32263] " pinskia at gcc dot gnu dot org
2007-06-08 20:18 ` pinskia at gcc dot gnu dot org
2007-06-11 16:35 ` appfault at hotmail dot com
2007-06-12 4:34 ` pinskia at gcc dot gnu dot org [this message]
2007-06-13 17:56 ` appfault at hotmail dot com
2007-12-02 21:35 ` pinskia at gcc dot gnu dot org
2007-12-06 17:27 ` appfault at hotmail dot com
2008-11-04 23:49 ` appfault at hotmail dot com
2008-11-05 20:12 ` pinskia at gcc dot gnu dot org
[not found] <bug-32263-4@http.gcc.gnu.org/bugzilla/>
2012-01-19 6:22 ` pinskia at gcc dot gnu.org
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=20070612043428.1773.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).