Re: Small patch for the QNX platform

[Mike Gorchak]

Hello, Ralf!

RW> Yes.  Thanks for your testing.  Please post the tests/testsuite.log
RW> file for the testing that you have already done.  Then please also
RW> reconfigure (or, if you are using separate build trees, set up another
RW> build tree) with qcc/QCC:
RW>   path/to/libtool/configure -C CC=qcc CXX=QCC
RW>   make
RW>   make -k check

Here is in attachment stdout/stderr and tests/testsuite.log output with 
qcc/QCC and enabled 3.3.5 GCC compiler. QNX 6.3.2 comes with 2.95.3 and 
3.3.5 gcc compilers by default (this one I'm using), QNX 6.4 uses 4.x GCC 
only. 2.95.3 and 3.3.5 could be switched between each other with qcc/QCC 
wrapper only, not thru the gcc -V3.3.5 etc. By default gcc uses 2.95.3 
compiler only.

I need to explain some QNX features, which could cause a lot of problem. By 
default gcc do not searching in the /usr/include and /usr/lib dirs, because 
of QSSL's politics who requires to use qcc/QCC wrappers for the development. 
qcc/QCC also provides usable switching between host/crossplatform different 
versions of gcc.

Do you still need output with plain gcc without qcc wrapper ? It is possible 
to specify path where libstdc++ is placed and pass -I/usr/include 
and -L/usr/lib to gcc to check if plain gcc still works.

RW> and send verbose results for that, too, including log.  For getting
RW> verbose output for the old and the new testsuite, please see the README
RW> file.

Here is current environment variables for the tests:

export CC="qcc -V3.3.5,gcc_ntox86"
export CXX="QCC -V3.3.5,gcc_ntox86"
export CFLAGS="-O3 -funroll-all-loops -I/usr/include"
export CXXFLAGS="-O3 -funroll-all-loops -I/usr/include"
export LDFLAGS="-L/usr/lib"

Looks like I specified verbose output for the one bunch of tests :-/ only. I 
will re-run it. I terminated the tests at test 42.

With best regards, Mike Gorchak.  E-mail: address@hidden

testsuite.log
Description: Binary data

stdout.log.gz
Description: GNU Zip compressed data