libtool issues

Klaus T. Aehlig aehlig at
Mon Jun 20 09:45:27 UTC 2011

Dear Stephen,

> Or one could instead modify devel/libtools, maybe something like this. 
> Rename bin/libtool to libexec/, and then rewrite the libtool 
> script as something like:
> #!/bin/sh
> PREFIX=/usr/local
> TEMPCCDIR=`mktemp -d -t /tmp`
> export PATH=${WRKDIR}:$PATH
> ${LN} -s ${LOCALBASE}/bin/${CC} ${TEMPCCDIR}/cc
> ${LN} -s ${LOCALBASE}/bin/${CXX} ${TEMPCCDIR}/c++
> ${PREFIX}/libexec/ $@
> rm -r ${TEMPCCDIR}

besides the obvious point that ${TMPCCDIR} should be under ${WRKDIR}, I'm
getting nervous reading ${LOCALBASE}/bin/${CC} which seems to assume that
${CC} is the name of a binary to be found in ${LOCALBASE}/bin; this might
well be if libtool is used in conjunction with USE_GCC -- but are you sure
that this will always be the case? devel/libtool does not have such a dependency,
and if using ccache (as I do on my machines) you get something like

/usr/ports/devel/libtool>make -V CC

Am I missing something which makes your suggested changes to devel/libtool still


More information about the freebsd-ports mailing list