From owner-freebsd-ports@FreeBSD.ORG Mon Jun 20 14:57:29 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD0D3106566C; Mon, 20 Jun 2011 14:57:29 +0000 (UTC) (envelope-from stephen@missouri.edu) Received: from wilberforce.math.missouri.edu (wilberforce.math.missouri.edu [128.206.184.213]) by mx1.freebsd.org (Postfix) with ESMTP id 778E78FC19; Mon, 20 Jun 2011 14:57:29 +0000 (UTC) Received: from [127.0.0.1] (wilberforce.math.missouri.edu [128.206.184.213]) by wilberforce.math.missouri.edu (8.14.4/8.14.4) with ESMTP id p5KEvRU3082604; Mon, 20 Jun 2011 09:57:28 -0500 (CDT) (envelope-from stephen@missouri.edu) Message-ID: <4DFF5FD7.4040108@missouri.edu> Date: Mon, 20 Jun 2011 09:57:27 -0500 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10 MIME-Version: 1.0 To: "Klaus T. Aehlig" References: <4DFEE295.3090204@missouri.edu> <20110620091828.GA16267@curry.linta.de> In-Reply-To: <20110620091828.GA16267@curry.linta.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "ports@FreeBSD.org" , Stas Timokhin , "ade@freebsd.org" Subject: Re: libtool issues X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jun 2011 14:57:29 -0000 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/libtool.sh, 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/libtool.sh $@ >> 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. Stephen