On Mon, Jan 25, 2016 at 3:12 AM, Thomas Dickey <dickey@xxxxxxx> wrote: > On Thu, Jan 21, 2016 at 10:11:47AM +0300, anatoly techtonik wrote: >> On Wed, Jan 13, 2016 at 1:19 PM, Thomas Dickey <dickey@xxxxxxx> wrote: >> > On Mon, Jan 11, 2016 at 02:05:49PM +0300, anatoly techtonik wrote: >> >> Hi, >> >> >> >> In this build on Ubuntu x86_64 autoconf is unable to find X11 >> >> libraries: >> >> https://travis-ci.org/techtonik/PDCurses/builds/101477536 >> >> However, it works with explicit configure option >> >> --x-libraries=/usr/lib/x86_64-linux-gnu >> >> https://travis-ci.org/techtonik/PDCurses/builds/101506738 >> >> >> >> It looks like the problem is PDCurses specific >> >> http://askubuntu.com/questions/539574/how-to-install-xaw-package-with-header-files/578003 >> >> probably because people rarely use Xaw. Anyway, how to fix >> >> it? Is it an autoconf bug? >> > >> > no - it is a bug in PDCurses' configure script, which assumes that the >> > libraries are in a directory "../lib" relative to the location of the >> > X headers. >> >> Thank for clarification. The ./configure script is autogenerated - at >> least this is said in headers >> "Generated by GNU Autoconf 2.61 for PDCurses 3.4." >> So, is it a bug in Autoconf? >> >> > You might find this to be useful: >> > >> > http://anonscm.debian.org/cgit/users/agmartin/pdcurses.git/ >> >> I see only two patches, one of which is said to be fixed upstream >> https://anonscm.debian.org/cgit/users/agmartin/pdcurses.git/tree/debian/patches >> I can't extract the solution for complication problem from them. > > So (referring to PDCurses 3.4) > this line in the configure script is the problem: > > mh_lib_dirs="$x_libraries `echo "$ac_x_includes $ac_x_header_dirs" | sed s/include/lib/g`" > > The problem is that 64-bit machines nowadays generally use lib64 - not lib, > as the script assumes. When I tweaked it by hand, I just edited that line. > > mh_lib_dirs="$x_libraries `echo "$ac_x_includes $ac_x_header_dirs" | sed s/include/lib64/g`" And this will break 32-bit machines, no? > But I prefer packages... > > Refreshing my memory, I see that Martin may not have _fixed_ that. > But I did, using a script in the debian/rules file. I'm attaching > that, for discussion. As this list is about autoconf, is it possible to fix it Autoconf way, without debian/rules? I thought that there is be some environment variable (or is there another setting storage) that ./configure should read to detect where includes and libs are located for the current system. -- anatoly t. _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf