unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: "Poussin, David L M" <d.poussin@imperial.ac.uk>
Cc: 27766@debbugs.gnu.org
Subject: bug#27766: Bug with Guile 2.0.22
Date: Wed, 19 Jul 2017 13:11:33 -0300	[thread overview]
Message-ID: <20170719131133.0f77e7c3@capac> (raw)
In-Reply-To: <6833B595-6357-4418-9EC7-F347EFF46911@imperial.ac.uk>

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

Hi David,

> 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.

> 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
> ...

In order to check that you (at least) have a proper guile installed first, try to run
guile 'on its own', open a terminal and just enter 'guile', or 'guile --version'

But anyway, I suggest you report this to the MIT Photonics bandgap maintainers,
because (a) there is no specific guile version checked at configure time, and the
manual states what guile version is expected..., then (b) it is very unlikely their
code will run with the latest guile stable verion, 2.2.2 (and prior to the 2.2
series, the latest was 2.0.14, not 2.0.22, for info)

	It seems the project was started 18y ago, the source code even refers
	to guile-1.2 ...

David

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2017-07-19 16:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19 10:18 bug#27766: Bug with Guile 2.0.22 Poussin, David L M
2017-07-19 16:11 ` David Pirotte [this message]
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=20170719131133.0f77e7c3@capac \
    --to=david@altosw.be \
    --cc=27766@debbugs.gnu.org \
    --cc=d.poussin@imperial.ac.uk \
    /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).