public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "appfault at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/32263] New: Document the required versions of glibc and binutils Date: Fri, 08 Jun 2007 20:06:00 -0000 [thread overview] Message-ID: <bug-32263-7959@http.gcc.gnu.org/bugzilla/> (raw) Document the required versions of glibc and binutils. Typically only a couple versions of glibc and binutils are compatible with each version of gcc, and finding out which ones are compatible is often quite time-consuming. While "gcc/doc/gccinstall.info" does document some minimum versions, it should also document maximum known-working versions as of the release date of gcc, since later versions invariably regress to being incompatible again. -- Summary: Document the required versions of glibc and binutils Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: appfault at hotmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32263
next reply other threads:[~2007-06-08 20:06 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-06-08 20:06 appfault at hotmail dot com [this message] 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 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
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-32263-7959@http.gcc.gnu.org/bugzilla/ \ --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: 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).