[MacPorts] #19237: libtool uses gsed but does not declare dependency (was: xorg-libXt: ../libtool: line 1: X--tag=CC: command not found)
MacPorts
noreply at macports.org
Wed Apr 8 05:25:46 PDT 2009
#19237: libtool uses gsed but does not declare dependency
-------------------------------------+--------------------------------------
Reporter: ryandesign@… | Owner: boeyms@…
Type: defect | Status: new
Priority: Normal | Milestone: Port Bugs
Component: ports | Version: 1.7.1
Keywords: | Port: libtool
-------------------------------------+--------------------------------------
Changes (by ryandesign@…):
* cc: jeremyhu@… (added)
* owner: jeremyhu@… => boeyms@…
* port: xorg-libXt => libtool
Comment:
Ok, you're right, 1.0.5_1 doesn't work anymore either. Looks like a
libtool issue. If I show the debug output I get:
{{{
---> Configuring xorg-libXt
DEBUG: Using compiler 'Mac OS X gcc 4.0'
DEBUG: Executing org.macports.configure (xorg-libXt)
DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.4'
DEBUG: Assembled command: 'cd "/opt/local/var/macports/build
/_Users_rschmidt_macports_dports_x11_xorg-libXt/work/libXt-1.0.5" &&
autoreconf --install -fvi'
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force
autoreconf: configure.ac: tracing
autoreconf: running: glibtoolize --copy --force
/opt/local/bin/glibtoolize: line 1: /opt/local/bin/gsed: No such file or
directory
/opt/local/bin/glibtoolize: line 1: /opt/local/bin/gsed: No such file or
directory
/opt/local/bin/glibtoolize: line 1: /opt/local/bin/gsed: No such file or
directory
/opt/local/bin/glibtoolize: line 1: /opt/local/bin/gsed: No such file or
directory
/opt/local/bin/glibtoolize: line 1: /opt/local/bin/gsed: No such file or
directory
/opt/local/bin/glibtoolize: line 1: /opt/local/bin/gsed: No such file or
directory
/opt/local/bin/glibtoolize: line 1: /opt/local/bin/gsed: No such file or
directory
/opt/local/bin/glibtoolize: line 1: /opt/local/bin/gsed: No such file or
directory
/opt/local/bin/glibtoolize: line 1: /opt/local/bin/gsed: No such file or
directory
/opt/local/bin/glibtoolize: line 1: /opt/local/bin/gsed: No such file or
directory
/opt/local/bin/glibtoolize: line 1: /opt/local/bin/gsed: No such file or
directory
/opt/local/bin/glibtoolize: line 1: /opt/local/bin/gsed: No such file or
directory
autoreconf: running: /opt/local/bin/autoconf --force
autoreconf: running: /opt/local/bin/autoheader --force
autoreconf: running: automake --add-missing --copy --force-missing
[snip]
}}}
So libtool is hardcoding the path to gsed into glibtoolize if gsed is
present at build time, though it does not declare a dependency on gsed,
therefore MacPorts did not tell me I was not supposed to uninstall gsed.
Since gsed has a few dependencies of its own, might be better to make
libtool always use the system's sed, even if gsed is present. (None of
those dependencies currently depend on libtool, but I'm worried one of
them might want to at some point, and that would be a circular
dependency.)
--
Ticket URL: <http://trac.macports.org/ticket/19237#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list