This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Patch for 64-bit HP-UX libstdc++-v3
- From: Steve Ellcey <sje at cup dot hp dot com>
- To: gcc-patches at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- Date: Fri, 15 Mar 2002 10:27:05 -0800 (PST)
- Subject: Re: Patch for 64-bit HP-UX libstdc++-v3
- Reply-to: sje at cup dot hp dot com
(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