Karl,
Thank you for all the time spent on this issue.
Yeah actually I am using automake 1.15.1 that comes with Linux Mint 19.2
distro:
automake/bionic,bionic,now 1:1.15.1-3ubuntu2 all [installed]
I saw you closed the ticket. good. Thanks again!
Regards,
Fabrizio
On Tue, Dec 8, 2020 at 9:20 PM K
Karl,
Sorry for the late reply.
Here are the sequence of the commands that show the issue described:
*Test use of relative path to identify external lib:*
$ tar xfz autotool-bug-rel.tar.gz
$ cd autotool-bug/proj
$ ./bootstrap.sh
$ ./configure --with-mylib=../lib
$ make
$ ls -la src/.deps
or just an unsupported condition that leads
to unexpected results.
Regards,
Fabrizio
On Tue, Nov 24, 2020 at 5:24 PM Hans-Bernhard Bröker
wrote:
> Am 24.11.2020 um 21:09 schrieb Fabrizio Bertocci:
> > Karl,
> > It took me a while to remember what this issue was about... but I
>
Karl,
It took me a while to remember what this issue was about... but I managed
to get to my old reproducer.
Ok, let me do one step back. The root problem is how do I ensure that paths
passed through ./configure command line are valid when building source code
under 'src' (for example).
Look at t
relative path.
I have a full reproducible project I could attach. Just let me know.
I have used this pattern for more than 10 years, but I don't remember ever
seeing this issue (although I attempted to use absolute paths only now).
Tested with newer systems like Linux Mint 19.2 as well as a bit older
systems like CentOS 7. Same problem on both.
Regards,
Fabrizio Bertocci
