[PATCH] hppa: Define __NO_LONG_DOUBLE_MATH so headers are consistent with libm build

[John David Anglin]

On 2015-12-13, at 6:11 PM, John David Anglin wrote:

> On 2015-12-13, at 5:12 PM, Chris Metcalf wrote:
> 
>> On 12/13/2015 5:02 PM, John David Anglin wrote:
>>> On 2015-12-13, at 4:42 PM, Chris Metcalf wrote:
>>> 
>>>> On 12/13/2015 4:13 AM, Andreas Schwab wrote:
>>>>> John David Anglin <dave.anglin@bell.net> writes:
>>>>> 
>>>>>> diff --git a/sysdeps/unix/sysv/linux/hppa/libc.abilist b/sysdeps/unix/sysv/linux/hppa/libc.abilist
>>>>>> index 1d30644..72435f8 100644
>>>>>> --- a/sysdeps/unix/sysv/linux/hppa/libc.abilist
>>>>>> +++ b/sysdeps/unix/sysv/linux/hppa/libc.abilist
>>>>>> @@ -263,6 +263,7 @@ GLIBC_2.2 __fcntl F
>>>>>> GLIBC_2.2 __ffs F
>>>>>> GLIBC_2.2 __finite F
>>>>>> GLIBC_2.2 __finitef F
>>>>>> +GLIBC_2.2 __finitel F
>>>>>> GLIBC_2.2 __flbf F
>>>>>> GLIBC_2.2 __fork F
>>>>>> GLIBC_2.2 __fpending F
>>>>>> @@ -294,9 +295,11 @@ GLIBC_2.2 __isdigit_l F
>>>>> You can't do that.  Please read the thread starting at
>>>>> <http://sourceware.org/ml/libc-alpha/2015-11/msg00564.html>.
>>>> I committed my fix, so I expect if you simply merge up to the tip of master,
>>>> the hppa abilist problem will go away too.
>>> 
>>> I'm testing a new version of the change with the versions changed to 2.23 and an update
>>> to the hppa/Versions file.
>>> 
>>> I'm not a glibc maintainer, so I shouldn't do the merge.
>> 
>> OK, but, if you are working on the glibc tip, you should not see these extra exports
>> for __finitel and friends at all any more, so you should not have to change your abilist files.
> 
> 
> Thanks, I'll retest with no changes to the hppa abi files.


There were no abi failures, so all that is needed is the original patch.  The v2 patch is withdrawn,

Dave
--
John David Anglin	dave.anglin@bell.net