public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mailboxnotfound at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/101843] Build of binutils-2.37 with gcc-11.2.0 fails due to change to libiberty/hashtab.c
Date: Wed, 11 Aug 2021 21:57:01 +0000	[thread overview]
Message-ID: <bug-101843-4-zcDG74CR40@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101843-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101843

--- Comment #6 from john henning <mailboxnotfound at yahoo dot com> ---
Let's simplify.

Per Richard's comment #1, there won't be a code fix.  OK.  
As to a doc fix, Richard wrote: 

  "For release versions your milage may vary and we fail to document working
version pairs"

YES - it would be nice if working pairs were documented in a list somewhere.
BUT - it might also be difficult to keep such a list updated.

So let's simplify.  How about if 
      https://gcc.gnu.org/install/download.html 
were to just include the generic advice that if you want to build them
together, then you should pick versions that were developed at about the same
timeframe.

(Yes, this is obvious advice once you understand that they have common
subdirectories, such as libiberty/.  But it was not obvious to at least one
user; and if that advice had been present, the user might have avoided a side
track.)

I've started to bat around possible specific language and perhaps will propose
a specific patch along these lines.

      parent reply	other threads:[~2021-08-11 21:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 10:59 [Bug other/101843] New: " mailboxnotfound at yahoo dot com
2021-08-10 12:06 ` [Bug bootstrap/101843] " rguenth at gcc dot gnu.org
2021-08-10 13:46 ` mailboxnotfound at yahoo dot com
2021-08-10 14:52 ` schwab@linux-m68k.org
2021-08-10 15:35 ` pinskia at gcc dot gnu.org
2021-08-10 16:05 ` mailboxnotfound at yahoo dot com
2021-08-11 21:57 ` mailboxnotfound at yahoo dot com [this message]

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-101843-4-zcDG74CR40@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: 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).