From: <dsmich@roadrunner.com>
To: guile-devel@gnu.org
Subject: guile-vm .go files in GUILE_LOAD_PATH
Date: Wed, 17 Sep 2008 18:57:19 -0400 [thread overview]
Message-ID: <27940045.1016601221692239870.JavaMail.root@cdptpa-web21-z02> (raw)
I've been tracking the guile-vm branch lately and had a recent problem. After much head scratching we finally figured out that a previously installed .go file was being used during the buld.
We (Andy and I on irc) hacked around it by creating a new environment variable that pre-inst-guile-env can use to override or disable things that libguile adds to the load-path. However, I think there is still a problem.
Basically, a .go file will be preferred over a .scm file even if the .scm file is earlier in the load-path. I think that the file earlier in the load-path should win.
Thoughts?
-Dale
next reply other threads:[~2008-09-17 22:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 22:57 dsmich [this message]
2008-09-18 3:55 ` guile-vm .go files in GUILE_LOAD_PATH David Séverin
2008-09-18 7:26 ` Neil Jerram
2008-09-18 18:40 ` Andy Wingo
-- strict thread matches above, loose matches on Subject: below --
2008-09-18 20:49 dsmich
2008-09-18 21:14 ` Andy Wingo
2008-09-18 22:32 ` 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=27940045.1016601221692239870.JavaMail.root@cdptpa-web21-z02 \
--to=dsmich@roadrunner.com \
--cc=guile-devel@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).