[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: build failures: string.h vs. HP-UX
From: |
Jim Meyering |
Subject: |
Re: build failures: string.h vs. HP-UX |
Date: |
Sat, 27 Jan 2007 08:16:48 +0100 |
address@hidden (Bob Proulx) wrote:
> Jim Meyering wrote:
>> Check out the red columns here:
>>
>> http://proulx.com:9000/
>>
>> Maybe a system-provided mempcpy macro is causing trouble?
>> ...
>> cc -I. -Ae -O -c mempcpy.c
>> cc: "string.h", line 39: error 1000: Unexpected symbol: "__dest".
>> cc: "string.h", line 39: error 1000: Unexpected symbol: "__src".
>> cc: "string.h", line 39: error 1573: Type of "__src" is undefined due to an
>> illegal declaration.
>
> Line 39 in the file is this:
>
> void *mempcpy (void *restrict __dest, void const *restrict __src, size_t
> __n);
Hi Bob,
Thanks for the info.
Can I get to the build directory for one of the losing systems?
Or just get a copy of its config.log?
That should tell us why the configure-time check for restrict isn't working.
- build failures: string.h vs. HP-UX, Jim Meyering, 2007/01/26
- Re: build failures: string.h vs. HP-UX, Bob Proulx, 2007/01/27
- Re: build failures: string.h vs. HP-UX,
Jim Meyering <=
- Re: build failures: string.h vs. HP-UX, Jim Meyering, 2007/01/27
- enforcing the use of string.h related modules, Bruno Haible, 2007/01/27
- Re: enforcing the use of string.h related modules, Eric Blake, 2007/01/27
- Re: enforcing the use of string.h related modules, Bruno Haible, 2007/01/31
- Re: enforcing the use of string.h related modules, Eric Blake, 2007/01/31
- Re: enforcing the use of string.h related modules, Bruno Haible, 2007/01/31
- Re: build failures: string.h vs. HP-UX, Bob Proulx, 2007/01/27
- Re: build failures: string.h vs. HP-UX, Bob Proulx, 2007/01/27
- Re: build failures: string.h vs. HP-UX, Jim Meyering, 2007/01/28
- Re: build failures: string.h vs. HP-UX, Paul Eggert, 2007/01/28