Hi there,
I’m trying to wrap my head around AC_FUNC_MMAP failing on AIX (specifically,
version 7.3 is what I tried on GCC compile farm). It appears that it has been
failing for decades though, so the problem isn’t exactly new...
It returns exit code 10, which means that the following comparison
pointers in shared memory) might desire a fixed mapping
>
> Bob
> On Jul 28, 2024, at 8:11 AM, "Yury V. Zaytsev" wrote: Hi
> there,
>
> I’m trying to wrap my head around AC_FUNC_MMAP failing on AIX (specifically,
> version 7.3 is what I tried on GCC compile farm).
Hi Zack,
> On 29. Jul 2024, at 15:36, Zack Weinberg wrote:
>
> We should probably also document the AIX issues in the "writing portable
> C programs" section of the manual if we don't already.
Yes, that would be nice. Something along the lines of…?
“N.B. AC_FUNC_MMAP is known to fail on IBM AI
Hey Paul,
Thank you very much for your exceptionally informative summary! Always very
nice hearing these stories straight from the horse’s mouth ;-)
All the best,
Yury
> On 29. Jul 2024, at 07:20, Paul Eggert wrote:
>
> On 2024-07-28 15:40, Bob Friesenhahn wrote:
>
>> Whoever wrote it had an
Hi Brooks,
> On 29. Jul 2024, at 23:42, Brooks Davis wrote:
>
> I wonder if AIX builds are producing SPEC1170-requesting programs
> most of the time, but not when building the autoconf code fragments?
> Otherwise I'd expect things to be failing more.
Thanks for the nudge in the right direction!
Hi Perry,
> On 1. Aug 2024, at 00:39, Perry Hutchison wrote:
>
> One could, at build time, include code to do something like (untested):
>
> if (strcmp(getenv("XPG_SUS_ENV", "ON")) != 0)
> {
>setenv("XPG_SUS_ENV", "ON", 1);
> }
>
> (and yes, if AIX has already tested XPG_SUS_ENV before
Hi Zack,
> On 31. Jul 2024, at 20:05, Zack Weinberg wrote:
>
> Thanks for digging into this, Yury. I have access to AIX machines via
> the GCC compile farm but I would not have been able to find this.
I’m also using the compile farm thanks to the great peoples of GCC who maintain
and provide
