Cplusplus-sig

Download

cplusplus-sig@python.org

May 2000

10 participants
32 discussions

[Steve Harris <sharris@primus.com>] Re: [C++-SIG] Problems building and testing CXX demo
by Steve Harris May 9, 2000

May 9, 2000

[accidentally mailed this directly to Marc]

1 0

Re: Problems building and testing CXX demo
by Steve Harris May 9, 2000

May 9, 2000

Phil Austin <phil(a)geog.ubc.ca> writes: > I can't help with most of this, but here's an example of a > successful build of python.o using KCC under solaris 2.6 [...] If I replace your KCC invocations with g++, I can get to this point by occasionally including a '-g' to overcome some problems with Sun's assembler. So I can get all of the object files compiled. This is where I get in trouble: > KCC python.o -o mypython -L/nfs/brant/local1/lib/python/solaris/lib/python1.5/config \ > -lpython1.5 -lm -lnsl -lsocket -ldl ./libcxx.so In my case, I translate this to look like: > g++ python.o -o mypython -L ~/usr/local/lib/python1.5/config \ -lpython1.5 -lm -lnsl -lsocket -ldl ./libcxx.so Undefined first referenced symbol in file in ./libcxx.so ld: fatal: Symbol referencing errors. No output written to mypython collect2: ld returned 1 exit status Note that there's a symbol "in" that's missing. I can use 'nm' to isolate that symbol: > nm ./libcxx.so | egrep '\|in$' [873] | 0| 0|NOTY |GLOB |0 |UNDEF |in At this point, I'm stumped. I can't find any such variable in the code. Any ideas what this could mean? [...] Thanks for your help so far. -- Steven E. Harris Primus Knowledge Solutions, Inc. http://www.primus.com

2 1