From: szgyg <szgyg@ludens.elte.hu>
To: guile-devel <guile-devel@gnu.org>
Subject: Guile HEAD on Cygwin-1.7
Date: Thu, 18 Jun 2009 09:33:33 +0200 [thread overview]
Message-ID: <4A39EDCD.1070609@ludens.elte.hu> (raw)
-*- outline -*-
Guile HEAD on the upcoming Cygwin-1.7 [1]
Good news first: I can't reproduce the infamous "threaded Guile hangs on
quit" error. (Cygwin has been shipping single-threaded Guile up to now.)
Guile builds with only minor hiccups. I hope these can be fixed before
the prerelease.
make check shows serious problems. I will investigate further.
s
[1] http://cygwin.com/ml/cygwin/2009-06/msg00346.html
* make
** configure and make with the same set of flags
Configuration test passes, make fails. Yes, -Werror.
cc1: warnings being treated as errors
../../libguile/gen-scmconfig.c: In function 'main':
../../libguile/gen-scmconfig.c:427: error: visibility attribute not
supported in this configuration; ignored
make[2]: *** [gen-scmconfig.o] Error 1
** pass -no-undefined when linking libguile_i18n
Other libs already have this.
** split the #ifdef in libguile/i18n.c line 59
Cygwin has langinfo.h, but not nl_types.h
** wrong path when compiling psyntax-pp.scm
First time only
Making all in module
make[2]: Entering directory `/home/szgyg/src/GIT/guile/=build/module'
/home/szgyg/src/GIT/guile/=build/meta/guile --no-autocompile -s
../../module/ice-9/compile-psyntax.scm \
../../module/ice-9/psyntax.scm
../../module/ice-9/psyntax-pp.scm
GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o
"ice-9/psyntax-pp.go" "ice-9/psyntax-pp.scm"
ERROR: In procedure open-file:
ERROR: No such file or directory: "ice-9/psyntax-pp.scm"
make[2]: *** [ice-9/psyntax-pp.go] Error 1
Subsequent makes use the correct path:
Making all in module
make[2]: Entering directory `/home/szgyg/src/GIT/guile/=build/module'
GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o
"ice-9/psyntax-pp.go" "../../module/ice-9/psyntax-pp.scm"
wrote `ice-9/psyntax-pp.go'
** readline is required, not optional
GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o
"ice-9/lineio.go" "../../module/ice-9/lineio.scm"
ERROR: readline is not provided in this Guile installation
make[2]: *** [ice-9/lineio.go] Error 1
* make check
** -Werror again
cc1: warnings being treated as errors
../../../test-suite/standalone/test-unwind.c: In function 'check_ports':
../../../test-suite/standalone/test-unwind.c:213: error: call to
'mktemp' declared with attribute warning: the use of `mktemp' is
dangerous; use `mkstemp' instead
make[4]: *** [test_unwind-test-unwind.o] Error 1
** stack overflow
I didn't dive into this yet. Any hint?
make[1]: Entering directory `/home/szgyg/src/GIT/guile/=build'
make check-TESTS
make[2]: Entering directory `/home/szgyg/src/GIT/guile/=build'
Testing /home/szgyg/src/GIT/guile/=build/meta/guile ...
with GUILE_LOAD_PATH=/home/szgyg/src/GIT/guile/test-suite
;;; note: autocompilation is enabled, set GUILE_AUTO_COMPILE=0
;;; or pass the --no-autocompile argument to disable.
;;; compiling /home/szgyg/src/GIT/guile/test-suite/lib.scm
;;; compiled
/home/szgyg/.guile-ccache/1.9//home/szgyg/src/GIT/guile/test-suite/lib.scm.go
ERROR: Stack overflow
Running alist.test
[...]
** segfault
On one occasion I got
make[1]: Entering directory `/home/szgyg/src/GIT/guile/=build'
make check-TESTS
make[2]: Entering directory `/home/szgyg/src/GIT/guile/=build'
Testing /home/szgyg/src/GIT/guile/=build/meta/guile ...
with GUILE_LOAD_PATH=/home/szgyg/src/GIT/guile/test-suite
/bin/sh: line 5: 3944 Segmentation fault (core dumped) ${dir}$tst
FAIL: check-guile
next reply other threads:[~2009-06-18 7:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 7:33 szgyg [this message]
2009-06-20 11:10 ` Guile HEAD on Cygwin-1.7 Andy Wingo
2009-06-27 13:36 ` szgyg
2009-06-28 21:09 ` Andy Wingo
2009-07-07 15:53 ` szgyg
2009-07-23 20:59 ` Andy Wingo
2009-07-25 16:14 ` szgyg
2009-07-26 13:12 ` Merging libguile-i18n with libguile Ludovic Courtès
2009-07-26 19:25 ` Andy Wingo
2009-07-27 22:56 ` Neil Jerram
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=4A39EDCD.1070609@ludens.elte.hu \
--to=szgyg@ludens.elte.hu \
--cc=guile-devel@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).