Hello, Ralf!
RW> please keep the mailing list in Cc:, thanks.
Sorry, my fault :)
RW> libtool does not take care to rename duplicate object members in
RW> archives on your system. Let's find out whether this is due to a
RW> deficient "sort" binary or func_basename on QNX: please cd into your
RW> build tree in which you ran the testsuite. Then enter these commands
RW> and post all their output (gzip large output):
RW> cd tests/testsuite.dir/16
RW> ./libtool --debug --mode=link --tag=CC qcc -V3.3.5,gcc_ntox86 -O3 \
RW> -funroll-all-loops -o libconv.la \
RW> 1/a.lo 2/a.lo 3/a.lo 4/a.lo 5/a.lo libc0.la
There is no tests/testsuite.dir/16 directory. I've 15, 17, 26, 35, 38, 68,
74 only. What do I need to create it ?
RW> 2) Failure test:
RW> does this work on your system?
RW> echo 'int not_main () { return 0; }' > a.c
RW> qcc -V3.3.5,gcc_ntox86 -O3 -funroll-all-loops -c a.c
RW> qcc -V3.3.5,gcc_ntox86 -O3 -funroll-all-loops -o a a.o
RW> echo $?
RW> ls -l a
Yes, it works. Reporting 0 as exit code and: ls -l a reports:
-rwxrwxr-x 1 root root 4110 Jan 27 08:13 a
ldd /ports/temp/libtool-2.2.6-qnx/a
/ports/temp/libtool-2.2.6-qnx/a
libc.so.2 => /usr/lib/ldqnx.so.2 (0xb0300000)
Is test code also contains 'int not_main () { return 0; }' as C code to
compile and link ?
RW> 3) The failure of the new versioning test. This is interesting:
>> P.S. Why tests which are marked at exit as "expected failure" did not
>> appeared in the testsuite.log file with 'ok' status ?
RW> Well, they fail. Each of them represents a bug we know about and
RW> should fix sometime. :-)
Ah, ok :)
With best regards, Mike Gorchak. E-mail: m...@malva.ua
