[MacPorts] #54112: autopen stuck on guile-2.0, refuses rebuild with guile-2.2.2
MacPorts
noreply at macports.org
Wed Jun 7 12:34:43 UTC 2017
#54112: autopen stuck on guile-2.0, refuses rebuild with guile-2.2.2
-------------------------+-----------------
Reporter: mouse07410 | Owner:
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: autogen |
-------------------------+-----------------
Comment (by gnw3):
The autogen tarball was created using guile-2.0 and the binary package for
autogen was linked against guile-2.0:
{{{
$ otool -L /opt/local/bin/autogen
/opt/local/bin/autogen:
/opt/local/lib/libopts.25.dylib (compatibility version 42.0.0,
current version 42.1.0)
/opt/local/lib/libguile-2.0.22.dylib (compatibility version
31.0.0, current version 31.1.0)
/opt/local/lib/libgc.1.dylib (compatibility version 2.0.0, current
version 2.3.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 1226.10.1)
/opt/local/lib/libintl.8.dylib (compatibility version 10.0.0,
current version 10.5.0)
}}}
I looked at what versions of guile and autogen are used elsewhere in my
lab:
Ubuntu 14.04 and RHEL7 use autogen-5.18 and guile-2.0.9. Msys2 uses
autogen-5.18.12 and guile-2.0.14.
In my view, we need a guile20 until GNU tarballs have moved to guile-2.2.
Hacking a configured
package to use newer tools puts macports outside the widely used
toolchains so has the
potential for introducing bugs not found in systems that stick with the
release configurations.
I have attached a guile20 Portfile that allows the binary autogen to run.
--
Ticket URL: <https://trac.macports.org/ticket/54112#comment:6>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list