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: Shared library annoyance with gcc-3_0-branch

To: Mark Mitchell <mark at codesourcery dot com>
Subject: Re: Shared library annoyance with gcc-3_0-branch
From: Andreas Jaeger <aj at suse dot de>
Date: 19 Feb 2001 13:21:33 +0100
Cc: lucier at math dot purdue dot edu, pfeifer at dbai dot tuwien dot ac dot at,jbuck at synopsys dot COM, gcc at gcc dot gnu dot org
References: <20010218121223S.mitchell@codesourcery.com><200102182118.f1ILIa028646@polya.math.purdue.edu><20010218183703F.mitchell@codesourcery.com>

Mark Mitchell <mark@codesourcery.com> writes:

> You can use -rpath if you want.  Or you can build --enable-static.  Or
> you can use -static-libgcc.  Or you can use -static.

AFAIK --enable-static builds all libs as static versions.  I'd like to
build only libgcc as static but have a shared libstdc++.  Is this
supported with the current configure frame-work?  Or should we change
gcc/configure to except --enable-static-libgcc?

Andreas 
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

Follow-Ups:
- Re: Shared library annoyance with gcc-3_0-branch
  - From: H . J . Lu
- Re: Shared library annoyance with gcc-3_0-branch
  - From: Alexandre Oliva

References:
- Re: Shared library annoyance with gcc-3_0-branch
  - From: Mark Mitchell
- Re: Shared library annoyance with gcc-3_0-branch
  - From: Brad Lucier
- Re: Shared library annoyance with gcc-3_0-branch
  - From: Mark Mitchell

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