This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc 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: [PATCH] PowerPC64 ELFv2 ABI 6/6: Bump ld.so soname version number


On Wed, 13 Nov 2013, Ulrich Weigand wrote:

> This is different for the long double check: if you don't have IBM long double,
> glibc will actually definitely not work, because it will use incompatible
> math library routines.  But building e.g. a big-endian ELFv2 glibc will work
> just fine from a technical perspective; I've in fact been using that for
> testing while we still have limited powerpc64le systems ...  It simply is
> not a configuration we will want to *support*.

It's not one we want to exist, in that it has GLIBC_* symbol versions not 
corresponding to any ABI that is expected to be stable.  I'm dubious of 
the --enable-hacker-mode option; I think we should just allow known valid 
configurations, give errors for others, and people adding new 
configurations can then change the configure script accordingly.

> > (And it looks 
> > like the check that little-endian powerpc32 isn't supported is still 
> > needed as well.)
> 
> Is this about this part of Alan's change here:
> 
> powerpc64*)     base_machine=powerpc machine=powerpc/powerpc64 ;;
> powerpc*)       base_machine=powerpc machine=powerpc/powerpc32 ;;
> 
> So I guess we shouldn't have the "*" in the second line?

Well - a reliable configure check would probably test if the compiler's in 
little-endian mode; removing the "*" would suffice in terms of existing 
practice, but isn't ideal.  There's a general mood towards making the 
compiler configuration, more than the configured host triplet and 
--with-cpu and --with-fp, determine how glibc is configured (so just as 
GCC can be configured for powerpc-linux-gnu and have both 32-bit and 
64-bit multilibs, so for glibc any powerpc*-*-linux* triplet should work 
with everything else being determined by configure from the compiler).

-- 
Joseph S. Myers
joseph@codesourcery.com


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