2013/8/23 Eli Zaretskii > > > I managed to go through the compilation process, > > and (after modifying meta/Makefile.am according to Eli's > > patch) to make install. > > This compilation process includes compiling all the Scheme files that > come with Guile. Since you say it succeeded, I don't understand what > you say later, see below. Do you see a lot of *.go files in the > directory where you built Guile? > When I enter the build directory and type $ find ./ -name '*.go' it seems that every .scm file from `modules' directory has its .go counterpart, > > When I ran guile-2.0, I got the following message: > > === > > Throw without catch before boot: > > Throw to key misc-error with args ("primitive-load-path" "Unable to find > > file ~S in load path" ("ice-9/boot-9") #f)Aborting. > > This seems to say that Guile cannot find its Scheme files. > > > Supplying GUILE_LOAD_PATH=/usr/share/guile/2.0 explicitly > > helped a little > > If that helped to avoid the failure to load, you probably didn't > specify a correct --prefix at configure time, or your "make install" > somehow didn't DTRT. > > I ./configured with --prefix=/usr (which is at the same mount point as / on my mingw configuration). When it comes to make install, I don't know what TRT would be > > but only during the first run -- it compiled some files from that > > directory and proceeded to the prompt. > > This is what I don't understand: which files it needed to compile, and > why? The compilation of Scheme files is part of the build process, > which you say you ran successfully to completion. What am I missing? > > I don't know either. > > but I'd truly appreciate some help. > > Let's start with the basics. Please describe: > > . Which build of what version of the GC library did you use, and > where did you get the Windows build of that library? Likewise for > other build dependencies, like libunistring, libiconv, etc. -- > please tell where you got each one of them. > > gc-7.2d compiled from the source from Hans Boehm's web site (I don't remember whether I finally configured it with pthreads or with windows threads, but I tried both for sure), gmp-5.2.1 from the source (I think it is shared version), libffi-3.0.13 from the source libunistring-0.9.3 from the source libiconv-1.14 and a few others bundled with mingw Everything built from the source was configured with --prefix=/usr . How did you configure Guile? If you used any --prefix argument, > please tell to which Windows directory does that prefix map on your > system? > Both / and /usr point to C:\MinGW\ Additionally, guile has been compiled with --program-suffix=-2.0 > . Did you see any warning or error messages during the build, and if > so, please show them. > > I can try to run the compilation for the second time, but surely there were no errors that would stop make from carrying on > . Did you see all the Scheme files being byte-compiled? > > Yes > . What command(s) did you use to install the built Guile? > > ./configure --without-threads --prefix=/usr make make install > . How do you run Guile after installing it? In particular, do you > run it from the MSYS Bash or from the Windows cmd window? > > So far I've been running it only in msys bash IOW, you didn't tell enough details about the build and the usage to > be able to guess what possible problems could be in your way. > > I'm eager to tell whatever is needed, if it could eventually help to get the process right. FWIW, I've successfully ran Guile from the Windows prompt after > building it, and successfully built GNU Make with Guile support. So > it's definitely possible to do that with MinGW. > > And would it be possible to distribute the binary release somehow? (in particular, the libguile.dll + scm/go modules that would be loaded from current directory)