From: <tomas@tuxteam.de>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: 2.9.5 build segfault on Ubuntu 18.04 [WAS: Nyacc and guile-nearly-3.0 (progress report)]
Date: Tue, 3 Dec 2019 17:43:31 +0100 [thread overview]
Message-ID: <20191203164331.GC12598@tuxteam.de> (raw)
In-Reply-To: <6218f387-2e14-fce2-921b-91351cbca68e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1412 bytes --]
On Mon, Dec 02, 2019 at 05:09:42PM -0800, Matt Wette wrote:
>
> On 12/2/19 6:28 AM, Matt Wette wrote:
> >I'm building 2.9.5 now but running into errors (ubuntu 18.04):
> >/bin/bash: line 6: 14657 Segmentation fault (core dumped)
> >GUILE_AUTO_COMPILE=0 ../meta/build-env guild compile
> >--target="x86_64-pc-linux-gnu" -O1 -Oresolve-primitives -L
> >"/home/mwette/proj/guile/guile-2.9.5/module" -L
> >"/home/mwette/proj/guile/guile-2.9.5/guile-readline" -o
> >"system/vm/linker.go" "../module/system/vm/linker.scm"
> So, as a random check, I first verified that I could reproduce the
> above error at the command line. I did.
>
> Then I removed "-Oresolve-primitives" and it compiled without
> error. Any help?
OK -- compiles successfully now. I realize in hindsight that
my answers sometimes went (only) to guile-devel, so I re-quote
that one where I "solved" configury:
> OK, solved this one -- will try to follow up with the rest.
>
> I just had to set GUILE_PROGS in etc/configure.ac besides GUILE_PKG,
> like so:
>
> GUILE_PKG([3.0])
> GUILE_PROGS([2.9.5])
>
> Configure now does "something". Next steps later.
So far, so good. Now it compiles "cleanly" (but there's no -Oresolve-primitives
option in sight in all of the compile; no idea why).
A cursory test (with the example from the man page)
shows signs of life. Yay!
Thanks
-- tomás
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2019-12-03 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191202094041.GA10353@tuxteam.de>
[not found] ` <20191202125507.GA14913@tuxteam.de>
[not found] ` <94784430-a9ad-bb11-f481-ef2426a6dfca@gmail.com>
2019-12-03 1:09 ` 2.9.5 build segfault on Ubuntu 18.04 [WAS: Nyacc and guile-nearly-3.0 (progress report)] Matt Wette
2019-12-03 9:15 ` tomas
2019-12-03 12:04 ` tomas
2019-12-03 16:43 ` tomas [this message]
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=20191203164331.GC12598@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=matt.wette@gmail.com \
/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).