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]
Other format:	[Raw text]

Re: Why are libgcc.a and libgcc_eh.a compiled with -fvisibility=hidden?

From: Ollie Wild <aaw at google dot com>
To: "H.J. Lu" <hjl dot tools at gmail dot com>
Cc: Jakub Jelinek <jakub at redhat dot com>, GCC Development <gcc at gcc dot gnu dot org>
Date: Thu, 8 Mar 2012 07:46:48 -0800
Subject: Re: Why are libgcc.a and libgcc_eh.a compiled with -fvisibility=hidden?
References: <CAFOgFcQwBnZR6SQ_kODmBQpY1x4FTrqyUGoZ1oDqSUVAj+_vvw@mail.gmail.com> <20120308083806.GV6148@sunsite.ms.mff.cuni.cz> <CAMe9rOr0MAhdQc+jkTTbUM6h60-dja9vb4VZhZV08-=kAm_d+g@mail.gmail.com>

On Thu, Mar 8, 2012 at 7:23 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
>
> If I understand it correctly, the reason Google doesn't want libgcc_s.so
> is Google believes GPLv3 exception only applies to libgcc,a and libgcc_eh,a,
> not libgcc_s.so. ?If GPLv3 exception also applies to libgcc_s.so, Google
> may consider using libgcc_s.so.

It's an internal process thing.

We're not worried about licensing in this context.

Ollie

References:
- Why are libgcc.a and libgcc_eh.a compiled with -fvisibility=hidden?
  - From: Ollie Wild
- Re: Why are libgcc.a and libgcc_eh.a compiled with -fvisibility=hidden?
  - From: Jakub Jelinek
- Re: Why are libgcc.a and libgcc_eh.a compiled with -fvisibility=hidden?
  - From: H.J. Lu

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