|
From: | Juergen Sauermann |
Subject: | Re: [Bug-apl] Bug: ./configure --without-libapl still wants to compile library |
Date: | Mon, 26 Dec 2016 23:35:14 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 |
Hi Alexey, first of all, --without-libapl is not a valid ./configure option, and there is no mentioning of --without-libapl in README-2-configure. Not building libapl is the default, so instead of saying --without-libapl you should simply not say --with-libapl. The --without-PACKAGE description in configure --help comes from the standard autoconf help and relates to packages being used and not to packages being produced (like libapl). As a matter of fact, according to ./configure --help, --without-libapl is the same as --with-libapl=no. Now, --with-libapl does not have (resp. ignores) any arguments, which makes --with-libapl=no the same as --with-libapl, which is what you see. /// Jürgen On 12/26/2016 09:09 PM, Alexey
Veretennikov wrote:
Hi, It seems what even if I set ./configure --without-libapl the configure scripts still reports checking if we want to build libapl.so... yes |
[Prev in Thread] | Current Thread | [Next in Thread] |