-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 5/1/10 3:11 PM, Jack Howarth wrote:
>    FYI, Steven Bosscher has made amazing progress towards
> implementing Mach-O link time optimization for FSF gcc
> working on my machine under fink...
> 
> http://gcc.gnu.org/ml/gcc-bugs/2010-05/msg00035.html
> 
> One issue I have run into though is how to reliably produce
> the necessary fink autoconf-2.64 package for regenerating
> configure files in FSF gcc (which requires exactly 2.64).
> Steven is now testing under i386 fink and I ran into the
> same random issue as before when trying to replace the
> stock autoconf file in unstable with one for 2.64. Using
> the autoconf.info of...
> 
> 

<snip>

- From the DescDetail of the current autoconf from unstable:

"This package installs Autoconf version 2.63. It has some compatibility
problems with older packages. If you want to work on a package that
requires
Autoconf 2.13, install the autoconf2.13 package instead. Because of
some major improvements in autoconf-2.64, that version is not
compatible either, for latest autoconf, please install the autoconf2.6
package."

It seems like we probably _don't_ want "autoconf" to be 2.64 based on
that, because that'll break build packages that expect to be compatible
with 2.63.

There's no way to generate your configure files with 2.65?
- -- 
Alexander Hansen
Fink User Liaison
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkvckbUACgkQB8UpO3rKjQ97EQCbBZFOx1l1WN9Xz9IANLVNHal7
fqkAn1uwCIP+3ivllsEYPWCYdExAxeql
=RcQw
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
_______________________________________________
Fink-devel mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to