[Ecls-list] Small problem with load paths

Andrew Topp talmakion at yahoo.com.au
Sun Jun 13 22:57:05 UTC 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm having an issue with the latest CVS of ECL. A while ago, using:

(setq *default-pathname-defaults* (make-pathname :directory '(:relative
"data" "lisp")))

Worked fine to allow loading of Lisp code contained in ./data/lisp
(under the application dir) without specifying a full path to LOAD. This
used to be in my application's init.lsp file, which was loaded using a
full path.

I've also tried:
(load "wrapper" :search-list (cons (make-pathname :directory '(:relative
"data" "lisp")) nil))

and:
(setq si::*load-search-list* (cons (make-pathname :directory '(:relative
"data" "lisp")) si::*load-search-list*))
(load "wrapper")

Neither of which work (being pretty much the same thing, anyway).

I've traced into cl_load, it tries to use the paths, and seems to return
the 'ok' value at line 239 of load.d after calling itself recursively,
but something fails, it doesn't actually return - just continues into
the code below there, and fails:

Filesystem error with pathname "wrapper".
Either the file cannot be accessed or the pathname is not a valid one.
Broken at LOAD.

I could be reading this problem incorrectly, since GDB sometimes has
problems processing .d files (off by a couple of lines, showing the
wrong info).

The file's name is data/lisp/wrapper.lsp

For now I'm using full paths in my code, but this is messy. Am I doing
something wrong, and the activity's been changed ?

Thanks,
- --
|> DeSigna (Andrew Topp)

GPG Public Key:
http://search.keyserver.net:11371/pks/lookup?op=get&search=0x76E841F6

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAzT3ep7NYgnboQfYRAuSSAKCQNLDXfatt64pdyDvnOA1d9fvxZwCgnLId
PG8KuAj6DECzbCZf7EuNhJU=
=4GuD
-----END PGP SIGNATURE-----




More information about the ecl-devel mailing list