Latest autoconf (2.63): problem generating libtool script when reconfiguring GCC (maybe others).
Tue Dec 9 18:33:00 GMT 2008
Dave Korn <dave.korn.cygwin <at> googlemail.com> writes:
> Hi gang (and Chuck in particular!)
Hi Dave, and welcome back,
> I've been having problems with the latest update to autoconf2.5 (2.63-1).
> The problem can be made to reliably appear and disappear by rolling my install
> forwards and back (to 2.61-1).
You may be better off asking on the gcc list. Ralf Wildenhues, in particular,
is most familiar with the effort to modernize gcc's usage of autoconf. But for
now, my understanding is that the entire gcc tree must be generated by 2.59 and
nothing else, because gcc includes a lot of hacks back-ported from newer
autoconf versions to make 2.59 work, but which might break when used side-by-
side with even newer autoconf versions where the upstream implementation has
moved on from the state where those hacks were extraced from.
I guess it boils down to: why are you rerunning autoconf anywhere in the gcc
tree in the first place? Are the configuration managed configure scripts
already in the gcc tree insufficient in some manner? Let's tackle the root
problem (what do you hope by regenerating java's configure) before worrying
about the secondary problem (why isn't a version of autoconf not yet supported
by the gcc team not working).
> I don't speak M4, and anyway this is just a distraction from the main job
> I was trying to do at the time, so this is as far as I've looked at it. I've
> kept the autom4te.cache dirs and trace logs around, in case they'll be of any
I know quite a bit about autoconf's use of m4 (in fact, I was the one that
built the upstream release of autoconf 2.63), but less about the gcc usage of
autoconf. But I personally have not attempted to build my own copy of gcc, nor
play with their hacks to make 2.59 still work. I'm not sure that your traces
will help me much; again, the gcc list may be a better resource.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin