From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roger Pau Monne Subject: Re: [PATCH v2] tools, configure: Fix LIB_PATH computation in configure scripts Date: Wed, 4 Jul 2012 12:31:29 +0100 Message-ID: <4FF42991.8080100@citrix.com> References: <1341399617.31696.43.camel@zakaz.uk.xensource.com> <4FF42848.6000906@citrix.com> <1341401256.31696.44.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1341401256.31696.44.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: "xen-devel@lists.xensource.com" , "Keir (Xen.org)" , Boris Ostrovsky , Ian Jackson , "roger.pau@entel.upc.edu" , Matt Wilson List-Id: xen-devel@lists.xenproject.org Ian Campbell wrote: > On Wed, 2012-07-04 at 12:26 +0100, Roger Pau Monne wrote: >> Ian Campbell wrote: >>> On Fri, 2012-06-08 at 21:23 +0100, Boris Ostrovsky wrote: >>>> # HG changeset patch >>>> # User Boris Ostrovsky >>>> # Date 1339185838 -7200 >>>> # Node ID fa21f847fc66619fad38923cd87d6ba51d731eba >>>> # Parent 32034d1914a607d7b6f1f060352b4cac973600f8 >>>> tools, configure: Fix LIB_PATH computation in configure scripts >>>> >>>> tool's configure script sets LIB_PATH by chopping off ${exec_prefix} >>>> from $libdir and it does so by computing length of ${exec_prefix} value. >>>> However, $libdir's value is a literal '${exec_prefix}/lib' string >>>> (i.e. $exec_prefix is not substituted) and therefore LIB_PATH may be >>>> computed incorrectly, most likely as "c_prefix}/lib64" assuming that >>>> exec_prefix is NONE. >>>> >>>> Instead, we should start at offset `expr length '${exec_prefix}/' >>>> (which is 15). >>>> >>>> Signed-off-by: Boris Ostrovsky >>> Boris, sorry for letting this languish for so long. >>> >>> Roger, any opinion on this patch? >> > >>> If I'm reading the script right this is the else clause of >>> [AS_IF([test "\${exec_prefix}/lib" = "$libdir"], >>> >>> so at this point we know libdir != ${exec_prefix}/lib, is there any >>> guarantee that it even starts with \${exec_prefix} ? >>> >>> I think this patch is complementary too rather than conflicting with / >>> subsumed by Matt's "tools: honour --libdir when it is passed >>> to ./configure" ? >> I think this patch is not needed anymore if we apply Matt's one, since >> Matt's patch gets rid of LIB_PATH usage, and instead uses exec_prefix >> and libdir directly. > > So Matt's patch could/should remove tools/m4/default_lib.m4? Yes, I've already replied to that thread also :)