🚀 go-pugleaf

In article <1992Jul24.220827.28092@jhunix.hcf.jhu.edu> camacs5@jhunix.hcf.jhu.edu (Sol Su) writes:
>i am trying to dynamically load compiled g++ code into
>S.  when the code is compiled with AT&T C++2.1 it loads
>without trouble; trying to get the g++-produced image
>into S yields "___builtin_delete" and "___builtin_new"
>undefined symbols.  in the libg++.a, indeed the ___builtin_delete
>symbol is U.  where is it resolved?

It's in -lgcc.  libgcc.a lives in the same place as the passes to
gcc, which you can find out by doing gcc -v.

It's not in libg++.a because libg++ is optional but support for new
and delete is required.  Also, libgcc routines can be included with
complete freedom in proprietary code (no GPL or even LGPL restrictions);
libg++ is subject to the LGPL.




--
Joe Buck	jbuck@ohm.berkeley.edu