From: Thomas Morley <thomasmorley65@gmail.com>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: GNU Guile 2.9.7 Released [beta]
Date: Sat, 14 Dec 2019 15:50:50 +0100 [thread overview]
Message-ID: <CABsfGyUS57CapXAXg1_KNUhHOXvcNwXzUxPW66kJdZg0m6+JPg@mail.gmail.com> (raw)
In-Reply-To: <89318b99-2a75-6965-5a28-aaa4ec5fa8f1@gmail.com>
Am Fr., 13. Dez. 2019 um 14:50 Uhr schrieb Matt Wette <matt.wette@gmail.com>:
>
>
> On 12/13/19 5:30 AM, Andy Wingo wrote:
> > We are pleased to announce GNU Guile release 2.9.7. This is the seventh
> > and hopefully next-to-last pre-release of what will eventually become
> > the 3.0 release series.
> >
>
> mwette$ uname -a
> Linux halibut 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC
> 2019 x86_64 x86_64 x86_64 GNU/Linux
>
> mwette$ ./configure --prefix=/opt/local
> ...
>
> mwette$ make
> ...
> wrote `system/vm/frame.go'
> BOOTSTRAP GUILEC system/vm/linker.go
> /bin/bash: line 6: 7565 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.7/module" -L
> "/home/mwette/proj/guile/guile-2.9.7/guile-readline" -o
> "system/vm/linker.go" "../module/system/vm/linker.scm"
> Makefile:1930: recipe for target 'system/vm/linker.go' failed
>
> Same happened on 2.9.5. Also, check this:
>
> mwette$ cd bootstrap
>
> mwette$ 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.7/module" -L
> "/home/mwette/proj/guile/guile-2.9.7/guile-readline" -o
> "system/vm/linker.go" "../module/system/vm/linker.scm"
> Segmentation fault (core dumped)
>
> mwette$ GUILE_AUTO_COMPILE=0 ../meta/build-env guild compile
> --target="x86_64-pc-linux-gnu" -O1 -L
> "/home/mwette/proj/guile/guile-2.9.7/module" -L
> "/home/mwette/proj/guile/guile-2.9.7/guile-readline" -o
> "system/vm/linker.go" "../module/system/vm/linker.scm"
> wrote `system/vm/linker.go'
>
> In the second case I removed "-Oresolve-primitives". I could not trace
> down further.
>
> Matt
>
>
FWIW,
I compiled successfully from current master, i.e.
~/guile-3.0 (master)$ git log
commit 4b34e1147693f5257720ae7545b001a400bbed91 (HEAD -> master, tag:
v2.9.7, origin/master, origin/HEAD)
Author: Andy Wingo <wingo@pobox.com>
Date: Fri Dec 13 13:57:04 2019 +0100
GNU Guile 2.9.7.
* GUILE-VERSION (GUILE_MICRO_VERSION): Bump.
* NEWS: Update.
with most simple:
sh autogen.sh
./configure
make
on my machine:
$ uname -a
Linux kasten 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
Though, I remember the same crashed at first attempt with 2.9.6
After doing
make clean
first, it worked finally.
Cheers,
Harm
next prev parent reply other threads:[~2019-12-14 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 13:30 GNU Guile 2.9.7 Released [beta] Andy Wingo
2019-12-13 13:50 ` Matt Wette
2019-12-14 14:50 ` Thomas Morley [this message]
2019-12-13 16:34 ` Jérémy Korwin-Zmijowski
2019-12-14 2:23 ` John Cowan
2019-12-14 7:40 ` tomas
2019-12-14 18:03 ` Amirouche Boubekki
2019-12-15 9:27 ` Amirouche Boubekki
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=CABsfGyUS57CapXAXg1_KNUhHOXvcNwXzUxPW66kJdZg0m6+JPg@mail.gmail.com \
--to=thomasmorley65@gmail.com \
--cc=guile-devel@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).