libtool issues

Stephen Montgomery-Smith stephen at
Mon Jun 20 14:57:29 UTC 2011

On 06/20/2011 04:18 AM, Klaus T. Aehlig wrote:
> 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 was thinking that libtool might be used in a situation other than a 
port build.

> ... 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
> /usr/local/libexec/ccache/world/cc
> /usr/ports/devel/libtool>
> Am I missing something which makes your suggested changes to devel/libtool still
> save?

I must admit that cache is something I didn't know about (nor do I fully 
understand).  But I am getting the feeling that you have found an issue 
that kills my second suggestion.


More information about the freebsd-ports mailing list