From: Geoffrey S. K. <ge...@kn...> - 2007-09-13 09:05:13
|
I added the following as the first sexp in src/build/make.scm: (display (src "")) to see just what JScheme thought the source path was, and it displayed: /Users/gknauth/test/jscheme/t-fresh/jscheme-7.2/src:/System/Library/ Frameworks/JavaVM.framework/Versions/1.5.0/Classes/.compatibility/src (That was all one one line, in case mail chopped it up.) I believe it was supposed to display just: /Users/gknauth/test/jscheme/t-fresh/jscheme-7.2/src In other words, the build process is trying to make the path to a filename, but the path contains more than one path element, so the filesystem errors back to Java, which reports back "No such file or directory." It's the path it's complaining about, not a missing version.txt file. version.txt is created by the (make-version) function call. There's a potential clue in the comment just before the definition of appDir in make.scm: ;;; Assumes a subdirectory is the only thing on classpath. (define appDir (.getCanonicalFile (.getParentFile (.getCanonicalFile (File. ($ "java.class.path")))))) (define srcDir (File. appDir "src")) (define (src name) (File. srcDir name)) It seems to me appDir needs to be fixed, because it is used in 20 places in make.scm to build subdirectory paths. |