http://www.riscos.info/bugzilla3/show_bug.cgi?id=209
John Tytgat <john.tyt...@aaug.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #1 from John Tytgat <john.tyt...@aaug.net> 2010-09-12 05:33:29 ---
I've recently reenabled the use of svnversion as part of cmunge version
identification and this requires a more recent version of automake/autoconf.
This used to be more trouble than this feature was worthwhile (hence, it got
backed out) but today we're already building specific versions for binutils and
gcc (again to avoid endless version problems) so we could use one of those.
My recent reenabling also ensured the use of automake/autoconf we're building
for binutils (as this are the most recent versions, i.e. automake 1.11.1 and
autoconf 2.64).
However, this gives intermediate problems when older versions were used in the
autoreconf process (here, automake 1.9) because you're locked on the versions
you initially used for that project. I've addressed this by enhancing the
'make clean' rule to remove all local files which are marked to be ignored for
'svn status', and this includes all local files which an autoreconf leaves
behind.
So, update to at least r4789, do 'make clean' and your reported build breakage
should be a thing of the past.
Thanks for the report.
--
Configure bugmail: http://www.riscos.info/bugzilla3/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
