unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Nyacc and guile-nearly-3.0
Date: Thu, 5 Dec 2019 09:28:05 +0100	[thread overview]
Message-ID: <20191205082804.GA4648@tuxteam.de> (raw)
In-Reply-To: <9ecf66ee-11ae-7ffc-f379-c0d3bcffe4f5@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 633 bytes --]

On Wed, Dec 04, 2019 at 04:48:33PM -0800, Matt Wette wrote:
> 
> 
> On 12/4/19 1:04 PM, tomas@tuxteam.de wrote:
> >
> >Matt says that he had to remove "-Oresolve-primitives" from the compiler
> >options. I hadn't -- but I suspect this option isn't set by default...
> >
> I apologize if I generated confusion.  I was intending to build
> 2.9.5 to help debug the nyacc issue.

d'oh :-)

> The segfault I ran into was in building guile-2.9.5.  It is
> uncorrelated with the nyacc issue.

Now everything is clear. Thanks, Mark. And thanks also for setting
me on the right path. And for nyacc...

Cheers
-- tomás

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2019-12-05  8:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02  9:40 Nyacc and guile-nearly-3.0 tomas
2019-12-02 12:55 ` Nyacc and guile-nearly-3.0 (progress report) tomas
2019-12-02 14:28   ` Matt Wette
2019-12-02 21:30     ` tomas
2019-12-03  9:25       ` Arne Babenhauserheide
2019-12-03 13:33         ` Matt Wette
2019-12-03 16:44           ` tomas
2019-12-02 21:45     ` tomas
2019-12-03  9:31       ` tomas
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 16:43       ` tomas
2019-12-04 19:12 ` Nyacc and guile-nearly-3.0 Amirouche Boubekki
2019-12-04 21:04   ` tomas
2019-12-05  0:48     ` Matt Wette
2019-12-05  8:28       ` 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=20191205082804.GA4648@tuxteam.de \
    --to=tomas@tuxteam.de \
    --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).