GNU bug report logs - #10693
guild compile --load-path value is not processed with scm_parse_path, GUILE_LOAD_PATH env variable value is parsed.

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Mark H Weaver <mhw <at> netris.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#10693: closed (guild compile --load-path value is not
 processed with scm_parse_path,  GUILE_LOAD_PATH env variable value is
 parsed.)
Date: Thu, 09 Feb 2012 03:35:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Wed, 08 Feb 2012 22:31:54 -0500
with message-id <874nv0wul1.fsf <at> netris.org>
and subject line Re: bug#10693: guild compile --load-path value is not processed with scm_parse_path, GUILE_LOAD_PATH env variable value is parsed.
has caused the debbugs.gnu.org bug report #10693,
regarding guild compile --load-path value is not processed with scm_parse_path,  GUILE_LOAD_PATH env variable value is parsed.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
10693: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10693
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Ian Hulin <ian <at> hulin.org.uk>
To: bug-guile <at> gnu.org
Subject: guild compile --load-path value is not processed with scm_parse_path, 
	GUILE_LOAD_PATH env variable value is parsed.
Date: Thu, 02 Feb 2012 00:46:34 +0000

Using this small test file load-path-test.scm using
meta/uninstalled-env bash with V2.0.5:

(eval-when (compile load eval)
(format #t "version: ~s\n" (version) )
(format #t "%load-path: ~s\n" %load-path)
(format #t "(access? (%search-load-path \"c++.scm\"): ~s\n"
  (%search-load-path "c++.scm")))

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 


1. Loading the test file (no extra %load-path items)

ian <at> nanny-ogg ~/src/lilypond (T2026-1)>> guile -l load-path-test.scm
;;; note: source file /home/ian/src/lilypond/load-path-test.scm
;;;       newer than compiled
/home/ian/Dropbox/Development/Guile-and-Scheme/guile-2.0.5/cache/guile/ccache/2.0-LE-4-2.0/home/ian/src/lilypond/load-path-test.scm.go
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;;       or pass the --no-auto-compile argument to disable.
;;; compiling /home/ian/src/lilypond/load-path-test.scm
version: "2.0.5"
%load-path:
("/home/ian/Dropbox/Development/Guile-and-Scheme/guile-2.0.5/module"
"/home/ian/Dropbox/Development/Guile-and-Scheme/guile-2.0.5/guile-readline"
"/home/ian/Dropbox/Development/Guile-and-Scheme/guile-2.0.5")
(access? (%search-load-path "c++.scm"): #f
;;; compiled
/home/ian/Dropbox/Development/Guile-and-Scheme/guile-2.0.5/cache/guile/ccache/2.0-LE-4-2.0/home/ian/src/lilypond/load-path-test.scm.go
version: "2.0.5"
%load-path:
("/home/ian/Dropbox/Development/Guile-and-Scheme/guile-2.0.5/module"
"/home/ian/Dropbox/Development/Guile-and-Scheme/guile-2.0.5/guile-readline"
"/home/ian/Dropbox/Development/Guile-and-Scheme/guile-2.0.5")
(access? (%search-load-path "c++.scm"): #f
# ^^^^^^^^^not found, not in %load-path - correct ^^^^^^^^^^^^
GNU Guile 2.0.5
Copyright (C) 1995-2012 Free Software Foundation, Inc.

Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
This program is free software, and you are welcome to redistribute it
under certain conditions; type `,show c' for details.

Enter `,help' for help.
scheme@(guile-user)> ,q
ian <at> nanny-ogg ~/src/lilypond (T2026-1)>>

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 

2. Loading the test file (extra %load-path items specified with
GUILE_LOAD_PATH environment variable)
ian <at> nanny-ogg ~/src/lilypond (T2026-1)>> env
GUILE_LOAD_PATH="/home/ian/src/lilypond:/home/ian/src/lilypond/scm"
guile -l load-path-test.scmversion: "2.0.5"
%load-path:
("/home/ian/Dropbox/Development/Guile-and-Scheme/guile-2.0.5"
"/home/ian/Dropbox/Development/Guile-and-Scheme/guile-2.0.5/guile-readline"
"/home/ian/Dropbox/Development/Guile-and-Scheme/guile-2.0.5/module"
"/home/ian/src/lilypond" "/home/ian/src/lilypond/scm")
#^^^^^^^^ env variable contents parsed with scm_parse_path ^^^^^^^^^^^
(access? (%search-load-path "c++.scm"):
"/home/ian/src/lilypond/scm/c++.scm"
#^^^^^^^^^^^^^^^^ file found - correct ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
GNU Guile 2.0.5
Copyright (C) 1995-2012 Free Software Foundation, Inc.

Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
This program is free software, and you are welcome to redistribute it
under certain conditions; type `,show c' for details.

Enter `,help' for help.
scheme@(guile-user)> ,q


>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 

3. Using guild-compile

ian <at> nanny-ogg ~/src/lilypond (T2026-1)>> guild compile
--load-path="/home/ian/src/lilypond:/home/ian/src/lilypond/scm"
--output=scm/out/load-path-test.go load-path-test.scm
version: "2.0.5"
%load-path: ("/home/ian/src/lilypond:/home/ian/src/lilypond/scm" "/home
# ^^^^^^^^^^^^^option string not parsed ^^^^^^^^^^^^^^^^^^^
/ian/Dropbox/Development/Guile-and-Scheme/guile-2.0.5/module"
"/home/ian/Dropbox/Development/Guile-and-Scheme/guile-2.0.5/guile-readline"
"/home/ian/Dropbox/Development/Guile-and-Scheme/guile-2.0.5")
(access? (%search-load-path "c++.scm"): #f
#^^^^^^^^^^^^^^ file not found in %load-path^^^^^^^^
wrote `scm/out/load-path-test.go'
ian <at> nanny-ogg ~/src/lilypond (T2026-1)>>

I get similar results using installed V2.0.5 on my laptop.

Cheers,

Ian Hulin

[Message part 3 (message/rfc822, inline)]

From: Mark H Weaver <mhw <at> netris.org>
To: ludo <at> gnu.org (Ludovic Courtès)
Cc: 10693-done <at> debbugs.gnu.org
Subject: Re: bug#10693: guild compile --load-path value is not processed with
	scm_parse_path, GUILE_LOAD_PATH env variable value is parsed.
Date: Wed, 08 Feb 2012 22:31:54 -0500

ludo <at> gnu.org (Ludovic Courtès) writes:

> Mark H Weaver <mhw <at> netris.org> skribis:
>
>> We might want to change the long option name (while continuing to accept
>> --load-path for backward compatibility), but I can't think of a good
>> name.  Any suggestions?
>
> As discussed on IRC, I agree that the long name can be misleading.
>
> Yet, I’d rather keep it, especially since the doc is non-ambiguous and
> ‘-L’ looks familiar.
>
> Done?  :-)

Okay, I'm closing this bug.

    Mark

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.