Problem with linking...

Problem with linking...

Post by Jason Richar » Thu, 25 Aug 1994 22:24:41



Hi,

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
   ___builtin_vec_delete

I didn't install Ptolemy in /users/ptolemy but I did set the
4 environment variables...

Cheers,
jason

 
 
 

Problem with linking...

Post by Jason Richar » Fri, 26 Aug 1994 11:40:53



: Hi,
:
: 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
:    ___builtin_vec_delete
:
: I didn't install Ptolemy in /users/ptolemy but I did set the
: 4 environment variables...
:
: Cheers,
: jason

I stupidly forgot to add that all is installed on a sun4...

Cheers,
jason

 
 
 

Problem with linking...

Post by Christopher Hylan » Fri, 26 Aug 1994 15:02:29



>   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
>      ___builtin_vec_delete

>   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.
Try:
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
from.

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
--
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.)

 
 
 

Problem with linking...

Post by Jason Richar » Sat, 27 Aug 1994 09:59:32


Thanks!!!

This is what happened:
I started to rebuild the system. Because of system limits, etc.
this wasn't possible. I installed Ptolemy again with the GNU compiler
shipped with Ptolemy. Due to an inconsistency with environment variables,
PTcl.o was compiled with g++ v2.6 rather than g++ v2.5.8. I needed to
compile PTcl.o, as it doesn't come with the binaries.

Anyway, It works again!

Much appreciated,
Jason

----------------


: 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.
: Try:
: 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
: from.
:
: 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
: --
: 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.)

 
 
 

1. Problem with links in Excel 5

I've had it, too.  Sometimes, you can use Edit/Links/Change Source and
point the linked file to itself to delete the link.  This won't always
fix it, but it commonly does.

--
Craig Ross              (313) 481-5228 (Voice)
Advanced Power Transfer (313) 481-5065 (Fax)
GM Powertrain           Remove the SPAM filter in my address to reply.

Speaking only for myself as no employer would possibly share my
opinions.

2. More comments on Backmaster

3. Sparkplug....strange

4. HELP! Excel macro problem with links

5. Extended Software Inventory Released!

6. a problem while linking

7. problem with mdlView_createSavedViewElement

8. Problem : Creating Link Annotations Using Acrobat SDK

9. acrobat reader IE problem w/ links

10. I'm having a problem with links in docs

11. Problems using Link-pdfmarks with Distiller

12. problems with links in p65