On June 23, 2005 at 19:03:26 EDT, Kyle Moffett wrote:
g++3 -o obj_Darwin_ppc_r/asnparser -I/sw/include -fno-common -
dynamic -fno-common -dynamic -L/sw/lib -lresolv -L../../lib ./
obj_Darwin_ppc_r/asn_grammar.o ./obj_Darwin_ppc_r/asn_lex.o ./
obj_Darwin_ppc_r/main.o -lpt_Darwin_ppc_r -lpthread -llber -lldap -
lldap_r -lssl -lcrypto -lexpat -lSDL -framework AudioToolbox -
framework CoreAudio
ld: Undefined symbols:
__ZTv0_n12_NSiD0Ev
__ZTv0_n12_NSiD1Ev
__ZTv0_n12_NSoD0Ev
__ZTv0_n12_NSoD1Ev
make[1]: *** [obj_Darwin_ppc_r/asnparser] Error 1
make: *** [opt] Error 2
### execution of make failed, exit code 2
Secondly, there are those undefined symbols. Do you know what
those symbols
are? I've been able to demangle the symbols with c++filt, and
here's what I
get:
virtual thunk to std::basic_istream<char, std::char_traits<char>
>::~basic_istream()
On Jul 18, 2005, at 09:59:23, David R. Morrison wrote:
Kyle:
The last errors you are getting look like a problem with mixing and
matching
various versions of the g++ ABI. The pwlib compile lines which you
showed
in your message are explicitly using g++ 3.1(via the g++3 command)
so you
cannot link to any libraries compiled with g++ 3.3 or g++ 4.0.
Please CC Shawn Hsiao on this as well, he's the listed maintainer, as
well as
an upstream GnomeMeeting/pwlib developer, and when he gets back from
vacation,
he'll probably be interested in the solution and patches :-D.
Hmm, *digs through sources*, after staring at this a bit more, I
can't see how
that could be related, unless gcc++3 isn't linking against the right
libstdc++.
Looking at the library and object list:
./obj_Darwin_ppc_r/asn_grammar.o ./obj_Darwin_ppc_r/asn_lex.o
./obj_Darwin_ppc_r/main.o -lpt_Darwin_ppc_r -lpthread -llber -lldap
-lldap_r
-lssl -lcrypto -lexpat -lSDL -framework AudioToolbox -framework
CoreAudio
The only C++ libraries and objects mentioned there are ones compiled
as a part
of pwlib, and I've grepped through the compile logs to verify that
all of the
files are compiled and linked with g++3 and nothing else. Thanks
anyways!
From some googling I did a while ago (although the same search terms
no longer
return the desired results now), I determined that those symbols
arise when
creating a subclass of istream or ostream in a user library, and that
such code
causes problems with ZeroLink, although that's completely irrelevant
here :-D.
Does anyone else have any ideas?
Cheers,
Kyle Moffett
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a18 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$ L++++(+
++) E
W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+ PGP+++ t+(+++) 5
X R?
tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$ r !y?(-)
------END GEEK CODE BLOCK------
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
