unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: joe <csfvjoe@gmail.com>
To: bug-guile@gnu.org
Subject: problem about v1.8.0 guile
Date: Thu, 13 Jan 2011 20:47:53 +0800	[thread overview]
Message-ID: <AANLkTimQvjUfzOUeXHtincaMTbGTotrgBhShxVfirEd6@mail.gmail.com> (raw)

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

Hello

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

      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

      I confirm two things. One is whole file structure is not changed. Two
is cgen-opc.scm still exists in relative path.

      I need you help for
      1. is there any change about file loading from v1.6.4 guile to v1.8.0
guile?
      2. could you give me suggestion of how to debug guile or debug scheme
codes?

Appreciate
joe

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

             reply	other threads:[~2011-01-13 12:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 12:47 joe [this message]
2011-01-13 23:25 ` problem about v1.8.0 guile Ludovic Courtès

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=AANLkTimQvjUfzOUeXHtincaMTbGTotrgBhShxVfirEd6@mail.gmail.com \
    --to=csfvjoe@gmail.com \
    --cc=bug-guile@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).