libc.so.1 link warning

I’ve downloaded the MySQL port from qnxstart, and am beginning to develop
client access programs. The port was done with/for 6.0 (not 6.1), and so the
client library requires the old libc.so.1. I get the following warning when
I link my client program.

qcc -lang-c++ -o mytest
mytest.o -L/usr/local/lib/mysql -lmysqlclient -lsocket
/usr/ntox86/bin/ld: warning: libc.so.1, needed by
/usr/local/lib/mysql/libmysqlclient.so, may conflict with libc.so.2

The program is very simple at this point and seems to operate correctly.
What kinds of symptoms should I look for that this message is warning me
about?

Is there any way to fix this without a rebuild of the MySQL port? The
distribution does not include source, and neither the qnxstart site nor the
distribution give a clue as to its source.

Thanks,
Marty Doane

Marty Doane <marty.doane@rapistan.com> wrote:

I’ve downloaded the MySQL port from qnxstart, and am beginning to develop
client access programs. The port was done with/for 6.0 (not 6.1), and so the
client library requires the old libc.so.1. I get the following warning when
I link my client program.

qcc -lang-c++ -o mytest
mytest.o -L/usr/local/lib/mysql -lmysqlclient -lsocket
/usr/ntox86/bin/ld: warning: libc.so.1, needed by
/usr/local/lib/mysql/libmysqlclient.so, may conflict with libc.so.2

The program is very simple at this point and seems to operate correctly.
What kinds of symptoms should I look for that this message is warning me
about?

Is there any way to fix this without a rebuild of the MySQL port? The
distribution does not include source, and neither the qnxstart site nor the
distribution give a clue as to its source.

You shouldn’t mix the two. However, it may work if you don’t have any
libc dependent structures in the API.

You could copy the old headers and libc from 6.0, then add them
to the include and link paths.

The best thing to do is to update the MySQL port though.


cburgess@qnx.com