From: Massimiliano Gubinelli <m.gubinelli@gmail.com>
To: John David Anglin <dave.anglin@bell.net>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Fix build of guile-3.0 trunk with gcc-8 on hpux11.11
Date: Mon, 23 Mar 2020 23:57:35 +0100 [thread overview]
Message-ID: <A3DF9F9A-E4B5-4C3D-B038-4D168DB1E9BC@gmail.com> (raw)
In-Reply-To: <mailman.1427.1584983864.3018.guile-devel@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 5004 bytes --]
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 <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 <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, guile-devel-request@gnu.org wrote:
>
>
> Message: 1
> Date: Mon, 23 Mar 2020 12:40:57 -0400
> From: John David Anglin <dave.anglin@bell.net <mailto:dave.anglin@bell.net>>
> To: guile-devel <guile-devel@gnu.org <mailto:guile-devel@gnu.org>>
> Cc: Helge Deller <deller@gmx.de <mailto:deller@gmx.de>>, John Paul Adrian Glaubitz
> <glaubitz@physik.fu-berlin.de <mailto:glaubitz@physik.fu-berlin.de>>
> Subject: [PATCH] Fix build of guile-3.0 trunk with gcc-8 on hpux11.11
> Message-ID: <1b543c79-7e66-9a93-8c57-91527519bac3@bell.net <mailto:1b543c79-7e66-9a93-8c57-91527519bac3@bell.net>>
> 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 bug-guile@gnu.org <mailto:bug-guile@gnu.org>
> ==================================
>
> 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
[-- Attachment #2: Type: text/html, Size: 66769 bytes --]
next parent reply other threads:[~2020-03-23 22:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1427.1584983864.3018.guile-devel@gnu.org>
2020-03-23 22:57 ` Massimiliano Gubinelli [this message]
2020-03-23 23:23 ` [PATCH] Fix build of guile-3.0 trunk with gcc-8 on hpux11.11 John David Anglin
2020-03-23 16:40 John David Anglin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A3DF9F9A-E4B5-4C3D-B038-4D168DB1E9BC@gmail.com \
--to=m.gubinelli@gmail.com \
--cc=dave.anglin@bell.net \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).