unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: joe <csfvjoe@gmail.com>
Cc: bug-guile@gnu.org
Subject: Re: problem about v1.8.0 guile
Date: Fri, 14 Jan 2011 00:25:01 +0100	[thread overview]
Message-ID: <87hbdc1j5e.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTimQvjUfzOUeXHtincaMTbGTotrgBhShxVfirEd6@mail.gmail.com> (joe's message of "Thu, 13 Jan 2011 20:47:53 +0800")

Hi,

joe <csfvjoe@gmail.com> writes:

>       Recently, we migrate scheme codes from v1.6.4 guile to v1.8.0 guile
> and go to build.

I warmly recommend 1.8.8, the latest release of the 1.8 series.

>       But, we get error message as below :
>               ERROR: In procedure primitive-load-path:
>               ERROR: Unable to find file
> "../../sid1/opcodes/../cgen/cgen-opc.scm" in load path

Dot-dot should be avoided in file names passed to ‘primitive-load-path’,
since that procedure searches for the given file in ‘%load-path’
(info "(guile) Loading").

>       1. is there any change about file loading from v1.6.4 guile to v1.8.0
> guile?

I don’t think so, but these are two very old releases.

>       2. could you give me suggestion of how to debug guile or debug scheme
> codes?

For the problem at hand, you could try the ‘search-path’ procedure to
see what happens, or use strace(1) to see where Guile is looking for
this file.

Hope this helps,
Ludo’.



      reply	other threads:[~2011-01-13 23:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 12:47 problem about v1.8.0 guile joe
2011-01-13 23:25 ` Ludovic Courtès [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=87hbdc1j5e.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guile@gnu.org \
    --cc=csfvjoe@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).