Opened 13 years ago
Closed 12 years ago
#32855 closed defect (worksforme)
automake 1.11.2 fails to compile
Reported by: | giordano.marcello@… | Owned by: | mww@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.3 |
Keywords: | Cc: | skymoo (Adam Mercer) | |
Port: | automake |
Description
automake 1.11.2 fails to compile because a recent enough version of autoconf cannot be found :
---> Verifying checksum(s) for automake ---> Checksumming automake-1.11.2.tar.bz2 ---> Extracting automake ---> Extracting automake-1.11.2.tar.bz2 ---> Configuring automake checking build system type... x86_64-apple-darwin11.2.0 checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... lib/install-sh -c -d checking for gawk... no checking for mawk... no checking for nawk... no checking for awk... awk checking whether make sets $(MAKE)... yes checking for perl... /opt/local/bin/perl checking whether /opt/local/bin/perl supports ithreads... no checking for tex... tex checking whether autoconf is installed... yes checking whether autoconf works... yes checking whether autoconf is recent enough... no configure: error: Autoconf 2.62 or better is required. shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_automake/automake/work/automake-1.11.2" && ./configure --prefix=/opt/local --infodir=/opt/local/share/info " returned error 1 Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details) Warning: the following items did not execute (for automake): org.macports.install org.macports.configure org.macports.build org.macports.destroot Log for automake is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_automake/automake/main.log Error: Unable to upgrade port: 1 To report a bug, see <http://guide.macports.org/#project.tickets>
the latest autoconf (2.68) is installed though. main.log attached
Attachments (2)
Change History (16)
Changed 13 years ago by giordano.marcello@…
comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | changed from macports-tickets@… to mww@… |
---|---|
Port: | automake added |
Changed 13 years ago by giordano.marcello@…
Attachment: | config.log added |
---|
comment:3 Changed 13 years ago by giordano.marcello@…
➜ ~ port -v installed autoconf The following ports are currently installed: autoconf @2.68_2 (active) platform='darwin 11' archs='noarch'
➜ ~ which autoconf /opt/local/bin/autoconf
➜ ~ autoconf --version autoconf (GNU Autoconf) 2.68 Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+/Autoconf: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>, <http://gnu.org/licenses/exceptions.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
config.log attached
comment:4 follow-up: 5 Changed 13 years ago by skymoo (Adam Mercer)
Configuration of automake appears to be picking up the system autoconf.
configure:2436: eval autoconf --version autoconf (GNU Autoconf) 2.61 Copyright (C) 2006 Free Software Foundation, Inc. This is free software. You may redistribute copies of it under the terms of the GNU General Public License <http://www.gnu.org/licenses/gpl.html>. There is NO WARRANTY, to the extent permitted by law. Written by David J. MacKenzie and Akim Demaille.
What is the output of:
$ autoconf --version
Have you modified the value of binpath
in ${prefix}/etc/macports/macports.conf
at all? What is binpath
set to?
comment:5 Changed 13 years ago by skymoo (Adam Mercer)
Replying to ram@…:
What is the output of:
$ autoconf --version
Ahh, I see you already ran this. Sorry.... That looks right so it's geting autoconf
from the system.
comment:6 Changed 13 years ago by giordano.marcello@…
➜ ~ cat /opt/local/etc/macports/macports.conf | grep -n1 prefix 4-# Set the directory in which to install ports. Must match where MacPorts itself is installed. 5:prefix /opt/local 6- -- 134- 135:binpath ${prefix}/bin:${prefix}/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/texbin
I think I added the /usr/texbin for having macports recognize my MacTex environment.
comment:7 Changed 13 years ago by skymoo (Adam Mercer)
That looks OK. In the past I've seen similar failures, in those cases the users had added /Developer/usr/bin
to binpath
, which clearly was a bad idea. But that isn't the case here...
Looks like you're running 10.7.2, what version of Xcode?
comment:8 Changed 13 years ago by giordano.marcello@…
Developer Information: Version: 4.2 (4D199) Location: /Developer Applications: Xcode: 4.2 (828) Instruments: 4.2 (4233) Dashcode: 3.0.2 (336) SDKs: Mac OS X: 10,6: (10K549) 10,7: (11C63) iPhone OS: 5,0: (9A334) iPhone Simulator: 5,0: (9A334)
comment:9 Changed 13 years ago by skymoo (Adam Mercer)
Xcode-4.2.1 has been available for a while now, but it's only a minor release so I doubt that will help...
I can't see any reason why this problem is happening, I have a very similar setup and can't reproduce this.
comment:10 Changed 13 years ago by giordano.marcello@…
Upgrading to Xcode-4.2.1 didn't help. Strangely, I downloaded sources for automake-1.11.2, extracted and tried to compile them and it worked, the right version of autoconf was picked.
comment:11 Changed 13 years ago by giordano.marcello@…
Replacing "${prefix}" with "/opt/local" in the binpath line in macports.conf fixed the issue.
Now idea why this worked though.
comment:14 Changed 12 years ago by mww@…
Resolution: | → worksforme |
---|---|
Status: | new → closed |
That's strange. Can you attach the config.log also? And can you show the output of: