[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bizarre linkage problem involving archives
From: |
Paul Pluzhnikov |
Subject: |
Re: Bizarre linkage problem involving archives |
Date: |
10 May 2004 19:42:23 -0700 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Artificial Intelligence) |
JoJoTwilligo@hotmail.com (Jo) writes:
> So shouldn't ../common/libcommon.a be just as good
> ../common/parameters_project.o?
Yes, it should.
To diagnose this further
- first verify that the file in ../common/libcommon.a is in fact
identical to ../common/parameters_project.o:
nm ../common/libcommon.a > junk.1
nm ../common/parameters_project.o > junk.2
diff junk.1 junk.2
- assuming they are, try this:
g++ ... -o executable ../mysql_support/libMySQLsupport.a \
../common/libcommon.a -Wl,-y,g_Log
The expected output is something like:
../mysql_support/libMySQLsupport.a(_sqlsession.o): reference to g_Log
../common/libcommon.a(parameters_project.o): definition of g_Log
You'll probably get different output, which may provide clues.
Cheers,
--
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.