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: dmj+ at andrew dot cmu dot edu
Subject: Re: Shared library annoyance with gcc-3_0-branch
From: Mark Mitchell <mark at codesourcery dot com>
Date: Mon, 19 Feb 2001 23:55:47 -0800
Cc: gcc at gcc dot gnu dot org
Organization: CodeSourcery, LLC
References: <20010219161704.A8150@drow.them.org>

>>>>> "Daniel" == Daniel Jacobowitz <dmj+@andrew.cmu.edu> writes:

    Daniel> Don't link against any shared libraries?  On at least
    Daniel> Linux systems, binaries in /bin and /sbin are not
    Daniel> statically linked.  -lc is implied.  My concern is whether

Then there shouldn't be any additional problem.  Wherever libc goes,
so must libgcc_s.so go.

    Daniel> libc will be linked against libgcc.so, or whether
    Daniel> applications using it will get their own copy.

I'm sorry.  I really don't understand the details of linker semantics
well enough to answer this.  I would assume libc would be linked
against libgcc, but it might not be.  I'm not sure.

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com

References:
- Re: Shared library annoyance with gcc-3_0-branch
  - From: Daniel Jacobowitz

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