Leopold Toetsch wrote:
> On Jun 29, 2006, at 18:48, Jarkko Hietaniemi wrote:
>
>> Any way to add verbosity to e.g. see which commands are being run?
>
> perl Configure.pl --verbose-step=snprintf
...
Testing snprintf...cc -std -D_INTRINSICS -fprm d -ieee -I/p/include
-DLANGUAGE_C -pthread -D_XOPEN_SOURCE=500 -I./include -c test.c
cxx -expect_unresolved '*' -O4 -msym -std -L/p/lib test.o -o test -lm
-lutil -lpthread -laio -lrt -lgmp -lreadline
./test
resolve_symbols: loader error: dlopen: libreadline.so.4: symbol
"tgetnum" unresolved
step auto::snprintf died during execution: Can't run the snprintf
testing program: at config/auto/snprintf.pm line 33.
"cxx" is the Tru64 C++ compiler.
(1) I don't know all those -libraries are being listed, the test
program certainly doesn't need them... yes, the linker should
know to ignore them as unused... but:
(2) This is not Linux so that -lgmp and -lreadline are not "standard"
but have been compiled and installed by the sysadmins (not admin)
and:
(3) They most definitely have not been compiled with cxx,
but most probably with gcc. And I have no idea whether
the libreadline.so actually works, since I haven't lately
tried to compile anything with it. In non-Linux systems
one cannot always assume installed GNU stuff works and/or
is uptodate...
Therefore, I am not surprised by the runtime linker getting cranky
when the "./test" is being run. (I have no idea who tries to call
"tgetnum", certainly not test.c.) If I remove the -lreadline from
the cxx line, the "./test" works fine giving:
borken snprintf: n = 1
as expected. I don't know how to start fixing this.
> leo
>
>
