* Olly Betts wrote on Tue, May 16, 2006 at 11:28:41AM CEST: > On 2006-05-16, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > Feel free, any kind of feedback is helpful. Esp. we're looking for > > packages that are broken by the new Autoconf, so that unintended > > incompatibilities can be fixed before the release. > > I've tried it now. I didn't have to modify any of the configure scripts > at all.
Any self-grown or third-party macros that use exit(3) in compile tests? > Otherwise everything seems much as before, except that some cross-builds > give a warning when they can't find a suitably crossed fortran compiler > and find a native one instead. > The warning is rather daft because I don't have any fortran code in > the project so I've no interest in what fortran compilers it can > or can't find. I guess it's libtool that's resulting in the configure > probe for a fortran compiler, which is a long standing issue I believe. > If that is meant to be fixed, something is going wrong. That is meant to be fixed, so that is a bug: CVS HEAD Libtool should not cause any Fortran tests unless you choose to. Can I reproduce this easily (maybe from the tarball link you posted earlier)? > Anyway, I'll leave it bootstrapping with CVS autoconf and libtool for > now, and update the versions from CVS periodically. Great -- thanks! Cheers, Ralf _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
