[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#23058: Bug found in libtool make process

From: Peter Rosin
Subject: bug#23058: Bug found in libtool make process
Date: Sat, 19 Mar 2016 22:40:56 +0100
User-agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0

On 2016-03-19 00:55, Villeneuve, Donald H wrote:
> Hi,
> We build and use libtool for one of the products we are working on.
> In the course of build libtool the following was noticed:
> 1)      Do as usual a configure  à everything seems fine
> 2)      export U=abcxyz_idoNotcare_whatitis
> 3)      make
> The make will fail because in the course of its run, it will use a variable 
> called $U.
> This bug was noticed when installing libtool 2.4.2 under
> Linux-2.6.32-504.el6.x86_64-x86_64-with-redhat-6.7-Santiago
> GNU Make 3.81
> The fix is clear: Someone must not use U as a variable name.  In this case, 
> the customer was using the variable U as follows:
>     export U=~/util
> So as a shortcut for their utility directory, which seems to be an admissible 
> use case.
> I’ve not check more recent versions of libtool against this bug.  But as we 
> move away from 2.4.2, it would be not to have to worry about this one.
> Thanks.
> If you have any further questions, more details can be provided.
> Donald

This is not a libtool bug, it is caused by some bad interaction
between autoconf and automake in the code for support of pre-ANSI
compilers. See [1] for an old dup of your report. Automake has
removed support for pre-ANSI compilers since a couple of years,
maybe it is time for autoconf to follow?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]