From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: guile-2.0 on mingw: the sequel
Date: Fri, 23 Aug 2013 11:29:27 +0200 [thread overview]
Message-ID: <CAMFYt2bvYrmYtwJTo-iUObTZNio=raesW7YgZZCs2zEj5yNTsw@mail.gmail.com> (raw)
In-Reply-To: <83vc2wj4hz.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 3875 bytes --]
2013/8/23 Eli Zaretskii <eliz@gnu.org>
>
> > 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)
[-- Attachment #2: Type: text/html, Size: 6951 bytes --]
next prev parent reply other threads:[~2013-08-23 9:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 20:25 guile-2.0 on mingw: the sequel Panicz Maciej Godek
2013-08-23 6:38 ` Eli Zaretskii
2013-08-23 9:29 ` Panicz Maciej Godek [this message]
2013-08-23 10:16 ` Eli Zaretskii
2013-08-23 20:14 ` Panicz Maciej Godek
2013-08-24 6:31 ` Eli Zaretskii
2013-08-24 8:05 ` Panicz Maciej Godek
2013-08-25 15:26 ` Eli Zaretskii
2013-08-25 16:59 ` Mark H Weaver
2013-08-25 17:47 ` Eli Zaretskii
2013-08-25 19:03 ` Ludovic Courtès
2013-08-25 19:34 ` Mark H Weaver
2013-08-27 21:51 ` Panicz Maciej Godek
2013-08-26 13:28 ` Eli Zaretskii
2013-08-23 15:13 ` Mark H Weaver
2013-08-23 15:34 ` Eli Zaretskii
2013-08-25 18:59 ` Ludovic Courtès
2013-08-25 21:19 ` Mark H Weaver
2013-08-26 2:35 ` Eli Zaretskii
2013-08-25 19:50 ` Mark H Weaver
2013-08-25 19:56 ` Mark H Weaver
2013-08-25 20:33 ` Eli Zaretskii
2013-08-25 20:40 ` Eli Zaretskii
2013-08-25 21:42 ` Mark H Weaver
2013-08-25 23:24 ` dsmich
2013-08-26 2:44 ` Eli Zaretskii
2013-08-26 5:56 ` Mark H Weaver
2013-08-26 6:26 ` Mark H Weaver
2013-08-26 13:10 ` Eli Zaretskii
2013-08-26 2:40 ` Eli Zaretskii
2013-08-25 20:32 ` Eli Zaretskii
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='CAMFYt2bvYrmYtwJTo-iUObTZNio=raesW7YgZZCs2zEj5yNTsw@mail.gmail.com' \
--to=godek.maciek@gmail.com \
--cc=eliz@gnu.org \
--cc=guile-user@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).