On Thu, 5 Sep 2013, Hélio Guilherme wrote:
Solved the linker problem with:
LDFLAGS=-L/usr/lib64
export LDFLAGS
./configure --enable-build-doc --enable-gtk3
---
There are a bunch of unknown results in commands to get machine
architecture. The first of them is:
/usr/bin/arch -k
/usr/bin/arch: invalid option -- 'k'
Try '/usr/bin/arch --help' for more information.
That's not a problem. The GNU autoconf mechanism is just running through a
bunch of tests which are known to work on some, but not all, systems. The
architecture is in fact picked up correctly by
/bin/arch = x86_64
while the "unknown" results are simply ignored.
---
So why didn't configure managed to get the correct arch? Can you improve
this?
As seen in your config.log, autoconf checks for a "site script" (whose
name is given by the value of the environment variable CONFIG_SITE, if
it's defined). On your system it's finding that $CONFIG_SITE evaluates to
/usr/share/site/x86_64-unknown-linux-gnu
and this file is being included. It seems to me that the problem may lie
there. A comment near the top says:
<quote>
# If user did not specify libdir, guess the correct target:
# Use lib64 for 64 bit bi-arch targets, keep the default for the rest.
</quote>
I'm not on a 64-bit system right now, but later today I can see how Fedora
19 handles this (gretl compiles correctly in 64-bit mode on FC 19 "out of
the box").
Allin