guile-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Fix build of guile-3.0 trunk with gcc-8 on hpux11.11


From: John David Anglin
Subject: Re: [PATCH] Fix build of guile-3.0 trunk with gcc-8 on hpux11.11
Date: Mon, 23 Mar 2020 19:23:22 -0400
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0

Hi Massimiliano,

I don't think so.  I have a recent build of bdwgc from github including this 
change:
https://github.com/ivmai/bdwgc/issues/308
The bdwgc testsuite is clean.

The patch that I submitted in issue 308 was to help in debugging issues with 
guile.  HEURISTIC2
causes faults during startup that aren't easy to get by using gdb.   I also 
submitted the previous
change to use HEURISTIC2 as the other techniques to determine the stack bottom 
were problematic
(e.g., with autogen).

The %zu issue causes immediate problems in the build due to incorrect type 
sizes.

The readdir issue fixes a testsuite issue.  As things stand, readdir64 is used 
in libguile and it's not available.

I think the issue with libatomic may also affect hppa-linux.  Some atomic 
support depends on LWS system
calls on hppa.  These are in libatomic.  On x86, it's only necessary to include 
libatomic.h and not link directly
with libatomic.  There's stuff in gcc testsuite to handle this.

Dave

On 2020-03-23 6:57 p.m., Massimiliano Gubinelli wrote:
> Hi John,
>  could maybe be a bug with the Boehm-gc? I had some recent issues compiling 
> Guile 2.2.7 in Haiku and discovered that there is a new version
> (8.1.0, next release development)  of the GC here
>
> https://github.com/ivmai/bdwgc
>
> which has some changes, in particular certain conditional compilations 
> related to HP/UX, see e.g. lines 2708, 3093, ... here:
>
> https://github.com/ivmai/bdwgc/blob/master/os_dep.c
>
> Maybe you could try to link this new version and see if the problem with the 
> test persist.
>
> Best
> Massimiliano
>
>> On 23. Mar 2020, at 18:17, address@hidden <mailto:address@hidden> wrote:
>>
>>
>> Message: 1
>> Date: Mon, 23 Mar 2020 12:40:57 -0400
>> From: John David Anglin <address@hidden <mailto:address@hidden>>
>> To: guile-devel <address@hidden <mailto:address@hidden>>
>> Cc: Helge Deller <address@hidden <mailto:address@hidden>>, John Paul Adrian 
>> Glaubitz
>> <address@hidden <mailto:address@hidden>>
>> Subject: [PATCH] Fix build of guile-3.0 trunk with gcc-8 on hpux11.11
>> Message-ID: <address@hidden <mailto:address@hidden>>
>> Content-Type: text/plain; charset=utf-8
>>
>> The following change fixes the build of guile-3.0 using gcc-8 on hpux11.11.
>> There are three issues addressed:
>>
>> 1) The printf function does not support %zu.  Since all the type sizes are 
>> small,
>> we can use %u and cast the sizeof results to unsigned int.
>>
>> 2) HP-UX 11.11 does not have readdir64 or readdir64_r.  The change adds back 
>> the
>> checks for readdir64 and readdir64_r.  I added support for readdir64 similar 
>> to that
>> for readdir64_r to gen-scmconfig.c and syscalls.h.
>>
>> 3) I needed to link libguile against gcc's libatomic. I don't have a 
>> configure fix yet.
>> So, I export "LIBS=-latomic" in my guild to get gcc's atomic routines. This 
>> fixed segmentation
>> fault building the texi documentation.
>>
>> With these changes, all tests pass except the following:
>>
>> wrote 
>> `/mnt/gnu/guile/objdir/cache/guile/ccache/3.0-BE-4-4.2/mnt/gnu/guile/guile
>> /test-suite/standalone/test-out-of-memory.go'
>> GC Warning: Failed to expand heap by 67239936 bytes
>> GC Warning: Failed to expand heap by 67108864 bytes
>> GC Warning: Out of Memory! Heap size: 1 MiB. Returning NULL!
>> GC Warning: Failed to expand heap by 1000132608 bytes
>> GC Warning: Failed to expand heap by 1000001536 bytes
>> GC Warning: Out of Memory! Heap size: 1 MiB. Returning NULL!
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 65536 bytes
>> GC Warning: Out of Memory! Heap size: 37 MiB. Returning NULL!
>> GC Warning: Failed to expand heap by 65536 bytes
>> GC Warning: Out of Memory! Heap size: 37 MiB. Returning NULL!
>> Warning: Unwind-only out of memory exception; skipping pre-unwind handler.
>> FAIL: test-out-of-memory
>> ==================================
>> 1 of 38 tests failed
>> (1 test was not run)
>> Please report to address@hidden <mailto:address@hidden>
>> ==================================
>>
>> Please install if okay.
>>
>> Guile is part of the build and test environment that I use for gcc.  HP-UX 
>> is still the only
>> environment where we have a working 64-bit compiler.  It is needed to build 
>> the 64-bit linux
>> kernel.
>>
>> Regards,
>> Dave Anglin
>


-- 
John David Anglin  address@hidden




reply via email to

[Prev in Thread] Current Thread [Next in Thread]