Patch for 64-bit HP-UX libstdc++-v3
Steve Ellcey
sje@cup.hp.com
Fri Mar 15 10:27:00 GMT 2002
(Sorry if this is a repeat, but I did get a bounce message from
gcc.gnu.org)
I just had a thought about this patch making libstdc++-v3 dependent on
libiberty. Isn't linking a shared library against an archive one
considered a bad thing? libstdc++-v3 can be built shared or archive but
it looks like libiberty is always archive only. Does this introduce
problems when libstdc++-v3 is linked against libiberty?
Steve Ellcey
sje@cup.hp.com
More information about the Libstdc++
mailing list