This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libiberty should be a shared library when cc1 has plugin enabled.
- From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- To: Basile Starynkevitch <basile at starynkevitch dot net>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 09 Jul 2009 12:54:23 +0100
- Subject: Re: libiberty should be a shared library when cc1 has plugin enabled.
- References: <20090709084949.GA27192@hector.lesours>
Basile Starynkevitch wrote:
> Hello All,
>
> Perhaps libiberty should be a shared library, not a static one, linked from
> cc1, when GCC has plugin enabled.
> We might also artificially add a reference to each libiberty function from
> cc1.
Or link it into cc1 et al. using "--whole-archive".
> If we did link dynamically libiberty.so:
We would also have to install it, and start worrying about library API
versioning and backward compatibility, or at any rate I think that's the main
reason why this has not been done in the pasy (cf. libbfd).
cheers,
DaveK