[MacPorts] #25509: autoreconf failure

Adam Mercer ram at macports.org
Sat Jul 3 21:59:36 PDT 2010


On Sat, Jul 3, 2010 at 23:36, Yiran Dong <dong5600 at uiuc.edu> wrote:
> Thank you very much for the reply.  I upgraded the autoconf to 2.66 by using
> the following commands:

<snip>

The release 2.66 has a couple of regressions with respect to 2.65, I
applied the upstream proposed patches to fix these regressions in the
2.66_1 MacPorts version. As you installed the vanilla 2.66 in
/usr/local[*] you will still run into these problems. Try the 2.66_1
version in MacPorts as this _should_ resolve these issues.

[*] having things installed in /usr/local is a bad idea as far as
MacPorts is concerned, it can lead to very strange build issues.


Cheers

Adam

PS: Upstream will be releasing a 2.67 shortly (probably in about 2
weeks, as the maintainer has just left gone on vacation) that should
resolve these issues.

PPS: There will probably be a 2.66_2 in MacPorts sometime in the next
couple of days as there is another minor regression...


More information about the macports-dev mailing list