Bug 16948 - recent binutils/bfd release tarballs generated with ancient autoconf version
Summary: recent binutils/bfd release tarballs generated with ancient autoconf version
Status: RESOLVED INVALID
Alias: None
Product: binutils
Classification: Unclassified
Component: binutils (show other bugs)
Version: 2.24
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks: 16370
  Show dependency tree / graph
 
Reported: 2014-05-15 15:46 UTC by maillist-gdb
Modified: 2022-11-24 05:04 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description maillist-gdb 2014-05-15 15:46:13 UTC 
the release tarballs of binutils 2.24 and gdb 7.6 were generated with an ancient autoconf version (2.64), which causes long-fixed and nasty bugs ( https://sourceware.org/bugzilla/show_bug.cgi?id=16370 gdb bug report ) to reraise from the dead.

to prevent such breakage in the future we should test for and deny running "make dist" successfully when the detected autoconf version is < 2.69.
Comment 1 Tom Tromey 2018-08-07 22:57:18 UTC 
I think the autoconf version bump in the binutils-gdb tree didn't
happen until well after these releases.
In binutils-gdb, the auto* output files are checked in and
everyone (including make dist) is required to use the identical
versions.  I'm not totally sure this is the best thing to do any
more, but it is current reality.

So, I tend to think this bug is invalid.
Comment 2 Alan Modra 2022-11-24 05:04:30 UTC 
.