> I was wondering if anyone has had any problems with the
> compiler shipped with the Ptolemy distribution.
> To cut a long story short, I had a problem linking
> using g++ v2.6. Rather than recompile the system,
> I decided to use the compiler that comes with the system.
> Well, my linking problems were fixed, but now I experience:
> ld: Undefined symbol
> I didn't install Ptolemy in /users/ptolemy but I did set the
> 4 environment variables...
Running 'nm -o libg++.a | grep builtin_vec_delete' shows that
builtin_vec_delete is undefined in the libg++-2.6.0 libg++.a
libg++.a:Obstack.o: U ___builtin_vec_delete
libg++.a:ioextend.o: U ___builtin_vec_delete
libg++.a:strstream.o: U ___builtin_vec_delete
libiostream.a:ioextend.o: U ___builtin_vec_delete
libiostream.a:strstream.o: U ___builtin_vec_delete
But that symbol is not present (defined or undefined) in the
libg++-2.5.3 that we ship with Ptolemy0.5:
One guess is that you have a .o or .a file that refers to this symbol.
nm -o $PTOLEMY/lib.$ARCH/* | grep vec_delete
You could also try running nm on all the .o files listed in the
pigiRpc compile step.
Another guess is that you are getting the wrong libraries during
compile or link time. This is where those four annoying environment
variables come in. Either remove gcc-2.6.0 and libg++-2.6 from your
path, or try setting the variables. Using the gcc '-v' option can be
useful here, it will show you where you are getting your libraries
Ptolemy0.5.1, due out in beta 'real soon now', should compile under
gcc-2.6.0/libg++-2.6, though we will be distributing binaries compiled
with gcc-2.5.8, as well as the gcc-2.5.8 compiler itself.
Christopher Hylands University of California
ph: (510)643-9841 fax:(510)642-2739 Berkeley, CA 94720-0001
home: (510)526-4010 (if busy -4068) (Office: 493 Cory. US Mail: 558 Cory.)