This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: GCC 3.0 Release Criteria

To: Joerg Faschingbauer <jfasch at hyperwave dot com>
Subject: Re: GCC 3.0 Release Criteria
From: Chip Salzenberg <chip at valinux dot com>
Date: Thu, 27 Apr 2000 17:29:37 -0700
Cc: Mark Mitchell <mark at codesourcery dot com>, gcc at gcc dot gnu dot org
References: <20000425235511A.mitchell@codesourcery.com> <200004260820.KAA15228@hwiw01.hyperwave.com>

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?
-- 
Chip Salzenberg              - a.k.a. -              <chip@valinux.com>
"I wanted to play hopscotch with the impenetrable mystery of existence,
    but he stepped in a wormhole and had to go in early."  // MST3K

Follow-Ups:
- Re: GCC 3.0 Release Criteria
  - From: Joerg Faschingbauer

References:
- GCC 3.0 Release Criteria
  - From: Mark Mitchell
- GCC 3.0 Release Criteria
  - From: Joerg Faschingbauer

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]