This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 3.0 Release Criteria
- To: Chip Salzenberg <chip at valinux dot com>
- Subject: Re: GCC 3.0 Release Criteria
- From: "David O'Brien" <obrien at NUXI dot com>
- Date: Mon, 1 May 2000 12:40:43 -0700
- Cc: Joerg Faschingbauer <jfasch at hyperwave dot com>, Mark Mitchell <mark at codesourcery dot com>, gcc at gcc dot gnu dot org
- Organization: The NUXI BSD group
- References: <20000425235511A.mitchell@codesourcery.com> <200004260820.KAA15228@hwiw01.hyperwave.com> <20000427172937.I570@perlsupport.com>
- Reply-To: obrien at NUXI dot com
On Thu, Apr 27, 2000 at 05:29:37PM -0700, Chip Salzenberg wrote:
> According to Joerg Faschingbauer:
> > The reason why I am asking is that the --enable-shared of current
> > releases (making libstdc++ a shared library) is mostly useless for
> > serious development. Releasing my programs, I cannot expect libstdc++
> > - generated with the same compiler version that I use to build with -
> > be present at the customer's site.
>
> Straw man, I think. If by "serious" you mean "targeting unknown
> systems", then you probably want to link with static libc also, yes?
I agree with Joerg. On FreeBSD platforms the abilility to easily
configure the GCC build to only create .a's is mandatory. Since you did
not buy Joerg's arguments, you will not buy mine. BUT meeting our needs
is easy, and you should allow others to develop their product as they see
fit.
--
-- David (obrien@NUXI.com)