From: Andy Wingo <wingo@pobox.com>
To: Jan Schukat <shookie@email.de>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 13848@debbugs.gnu.org
Subject: bug#13848: Statically linking guile-2.0.
Date: Sun, 10 Mar 2013 00:06:24 +0100 [thread overview]
Message-ID: <87txokxjf3.fsf@pobox.com> (raw)
In-Reply-To: <513B3CDA.1010409@email.de> (Jan Schukat's message of "Sat, 09 Mar 2013 14:44:58 +0100")
On Sat 09 Mar 2013 14:44, Jan Schukat <shookie@email.de> writes:
> Just tried it again on windows/mingw with the newer tarball:
>
> http://hydra.nixos.org/build/4290536/download/3/guile-2.0.7.157-929d1.tar.gz
FWIW it seems hydra is totally down right now; of course that would
happen as soon as ludo goes on holiday ;)
Here is a tarball I just generated from make dist:
http://wingolog.org/priv/guile-2.0.7.179-94c5.tar.gz
> checking for gcc... gcc
> checking whether the C compiler works... no
> configure: error: in `/c/Users/shookie/guiletest/lib/guile-2.0':
> configure: error: C compiler cannot create executables
No idea what is happening here, this looks like a problem on your side.
I fixed a bunch of things today. BTW are you using the old mingw or are
you using mingw32 or mingw64? It seems that the mingw64 project (which
provides both 32- and 64-bit builds) is the current thing, but I don't
really know.
Anyway, please give the new tarball a roll and see how it works for you.
Be sure to have a relatively new mingw. I built everything myself, with
all default options (except --enable-threads=pthreads in bdw-gc, and
enabling dynamic builds in gmp), and it builds with only some warnings
about iconv (filed with gnulib). I can't get it to run under wine
however, and that must mean something is pretty wrong...
Happy hacking,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2013-03-09 23:06 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 16:19 bug#13848: Statically linking guile-2.0 Jan Schukat
2013-03-02 15:28 ` Ludovic Courtès
2013-03-03 23:20 ` Jan Schukat
2013-03-05 0:54 ` Jan Schukat
2013-03-05 10:22 ` Ludovic Courtès
2013-03-05 15:44 ` Jan Schukat
2013-03-05 17:25 ` Ludovic Courtès
2013-03-05 22:25 ` Jan Schukat
2013-03-06 23:12 ` Ludovic Courtès
2013-03-09 13:44 ` Jan Schukat
2013-03-09 23:06 ` Andy Wingo [this message]
2013-03-09 23:57 ` shookie
2013-03-10 4:09 ` shookie
2013-03-10 17:32 ` Andy Wingo
2013-03-10 18:54 ` shookie
2013-03-10 19:23 ` Andy Wingo
2013-03-10 21:17 ` shookie
2013-03-10 22:03 ` shookie
2013-03-10 22:53 ` Andy Wingo
2013-03-11 0:07 ` shookie
2013-03-11 1:43 ` shookie
2013-03-11 8:26 ` Andy Wingo
2013-03-11 9:30 ` shookie
2013-03-13 9:30 ` Andy Wingo
2013-03-13 19:04 ` bug#13848: Aw: " Jan Schukat
2013-03-16 1:36 ` Jan Schukat
2013-03-29 19:35 ` Ludovic Courtès
2013-03-30 0:20 ` Jan Schukat
2013-03-30 21:27 ` Ludovic Courtès
2013-04-05 23:14 ` Jan Schukat
2013-04-07 10:20 ` Ludovic Courtès
2013-04-07 16:20 ` bug#13848: Aw: " Jan Schukat
2013-04-07 18:22 ` Andy Wingo
2013-04-07 19:18 ` bug#13848: Aw: " Jan Schukat
2013-04-07 20:00 ` Ludovic Courtès
2013-04-07 21:06 ` bug#13848: Aw: " Jan Schukat
2013-04-08 7:48 ` Ludovic Courtès
2013-03-10 17:38 ` shookie
2013-03-10 17:38 ` shookie
2013-03-14 13:54 ` Ludovic Courtès
2013-03-09 9:32 ` Andy Wingo
2013-03-09 15:42 ` Jan Schukat
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=87txokxjf3.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=13848@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=shookie@email.de \
/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).