AVR C Runtime Library - Bugs: bug #13416, autoconf version does not match...
You are not allowed to post comments on this tracker with your current authentication level.
bug #13416: autoconf version does not match various AVR Libc config files
Submitter: | None | ||
Submitted: | Thu 16 Jun 2005 05:31:26 AM UTC | ||
Category: | None | Severity: | 3 - Normal |
Priority: | 5 - Normal | Item Group: | None |
Status: | None | Assigned to: | None |
Percent Complete: | 0% | Originator Email: | -email is unavailable- |
Open/Closed: | Closed | Release: | None |
Fixed Release: | None |
Fri 22 Jul 2005 08:29:38 PM UTC, comment #2: |
Joerg Wunsch <joerg_wunsch> |
Sun 03 Jul 2005 06:26:49 PM UTC, comment #1: I have explored this a little further and found that the problem is caused by running reconf in this environment. It radically changes the aclocal.m4 file, setting it so it expects the newer version of autoconf while the scripts have all been made with the older version. The difference between the old scripts (which were not rebuilt with reconf) and the new m4 settings is what causes the problem. I have attached the resulting aclocal.m4 file.
|
John Altstadt <altstadt> |
Thu 16 Jun 2005 05:31:26 AM UTC, original submission:
While trying to build the AVR toolchain for Linux using the Moffitt/Erasmus shell scripts on an up to date Gentoo system, I ran in to the problem where the AVR Libc build failed with the error:
|
Anonymous |
Depends on the following items: None found
Items that depend on this one: None found
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2005-07-22 | joerg_wunsch | Open/Closed | Open | Closed | |
2005-07-03 | altstadt | Attached File | - | Added aclocal.m4, #2652 | |
2005-06-16 | None | Carbon-Copy | - | Added altstadt --AT-- telus --DOT-- net |
Powered by Savane 3.13-f8d8.
Corresponding source code
Sorry, this all looks like an autoconf problem to me.
I've been using autoconf-1.4 (called by that name) in order to
run ./reconf before releasing the tarball, but I've also
observed several oddities during that process. E.g. if that
tool is called "autoconf14" (FreeBSD's default), it will insist
on finding autoconf-1.4 upon "make distcheck".
It's probably best if you don't have any of these tools without
the version numbers appended in your $PATH at all -- at least
that's my experience. Send your thanks to the autoconf authors
for not providing fully backwards-compatible versions of their
tools.