Re: clang and static linking?

From: Steve Kargl <sgk_at_troutmask.apl.washington.edu>
Date: Fri, 9 Nov 2012 08:43:04 -0800
On Fri, Nov 09, 2012 at 02:00:12PM +0200, Konstantin Belousov wrote:
> On Thu, Nov 08, 2012 at 03:49:32PM -0800, Steve Kargl wrote:
> > 
> > This appears to fix the problem.  Don't know if this is
> > th right way to handle it.
> > 
> > Index: src/s_isnan.c
> > ===================================================================
> > --- src/s_isnan.c	(revision 242701)
> > +++ src/s_isnan.c	(working copy)
> > _at__at_ -40,7 +40,6 _at__at_
>
> Is this patch against src/msun ?

Yes.

> This is only a workaround, which break ABI and older binaries.

Which leads to an interest question.  With the major upheavel
of switching to clang, are there any ABI breaking changes that
would be desirable to commit?  This would entail a major library
version bump.  For starters, libc/gen/isnan.c could be removed.

> The bug is apparently in clang, which inserts the undef reference
> into the resulting object file, when weak alias references undefined
> symbol. Gnu as does not have the bug.
> 
> There is some magic switch to reduce amount of clang bugs, like
> -fno-integrated-as. Please try to compile the problematic .o with the
> switch.

I'll try this shortly.  Does this mean that we need to build
all *.a libraries where a weak reference may occur with this
switch?

-- 
Steve
Received on Fri Nov 09 2012 - 15:43:11 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:32 UTC