unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: "Poussin, David L M" <d.poussin@imperial.ac.uk>
To: 27766@debbugs.gnu.org
Subject: bug#27766: Bug with Guile 2.0.22
Date: Wed, 19 Jul 2017 10:18:23 +0000	[thread overview]
Message-ID: <6833B595-6357-4418-9EC7-F347EFF46911@imperial.ac.uk> (raw)

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

Dear Sir or Madam,

My name is David Poussin, I am a PHD in Imperial College London.

For my study, I try to use a simulation software named “ MIT Photonics bandgap “.
This software uses the guile library for part of its calculation.

However, when I try to launch it I obtain this error.


David$ mpb

Backtrace:

In ice-9/boot-9.scm:

 160: 11 Exception thrown while printing backtrace:

ERROR: In procedure private-lookup: Module named (system vm frame) does not exist


ERROR: In procedure scm-error:

ERROR: no code for module (system base compile)



It seems this error comes from Guile.

I searched a little bit and the software I try to use calls a previous version of Guile , v2.0.22.

I tried to download the latest version, but after, the MIT software does not recognise it.


I am using a MAC OS Sierra, version 10.12.5.


Do you know where my error comes from?


Thank you by advance,

David Poussin

[-- Attachment #2: Type: text/html, Size: 4328 bytes --]

             reply	other threads:[~2017-07-19 10:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19 10:18 Poussin, David L M [this message]
2017-07-19 16:11 ` bug#27766: Bug with Guile 2.0.22 David Pirotte
2017-07-19 16:15   ` David Pirotte

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=6833B595-6357-4418-9EC7-F347EFF46911@imperial.ac.uk \
    --to=d.poussin@imperial.ac.uk \
    --cc=27766@debbugs.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).