From: Kiyoshi KANAZAWA <yoi_no_myoujou@yahoo.co.jp>
To: 22509@debbugs.gnu.org
Subject: bug#22509: [guile-2.1.1 alpha] make check FAIL & crirical warnings on Solaris10 x86/64
Date: Mon, 1 Feb 2016 07:51:09 +0900 (JST) [thread overview]
Message-ID: <175856.3892.qm@web101213.mail.kks.yahoo.co.jp> (raw)
[-- Attachment #1: Type: text/plain, Size: 3999 bytes --]
Hello,
I tried alpha release of guile-2.1.1 on Solaris10 x86/64 with gcc 4.8.5.
Used -m32 to make 32 bit targets.
1. make check FAILs
FAIL: ports.test: %file-port-name-canonicalization: relative canonicalization with / - arguments: (expected-value "dev/null" actual-value "devices/pseudo/mm@0:null")
FAIL: time.test: strftime: C99 %z format: EST+5
FAIL: check-guile
I guess the 1st one can be ignored.
2. Critical warning in make check
;;; warning: max diff 2.0 > (sqrt 4.0)
3. Critical warning in make
hash.c:115:3: warning: left shift count >= width of type [enabled by default]
hash.c:124:3: warning: left shift count >= width of type [enabled by default]
hash.c:213:5: warning: left shift count >= width of type [enabled by default]
4. "warning: possibly unbound variable" in make
ice-9/readline.scm:127:38: warning: possibly unbound variable `readline-options-interface'
ice-9/readline.scm:158:4: warning: possibly unbound variable `%readline'
ice-9/readline.scm:208:4: warning: possibly unbound variable `*readline-completion-function*'
ice-9/readline.scm:212:2: warning: possibly unbound variable `*readline-completion-function*'
ice-9/readline.scm:215:10: warning: possibly unbound variable `*readline-completion-function*'
ice-9/readline.scm:218:10: warning: possibly unbound variable `*readline-completion-function*'
ice-9/readline.scm:64:0: warning: possibly unbound variable `readline-options-interface'
ice-9/readline.scm:98:49: warning: possibly unbound variable `%readline'
ice-9/runq.scm:93:8: warning: possibly unbound variable `apply-to-args'
language/ecmascript/base.scm:229:22: warning: possibly unbound variable `Boolean'
language/ecmascript/base.scm:230:21: warning: possibly unbound variable `String'
language/ecmascript/base.scm:231:21: warning: possibly unbound variable `Number'
language/ecmascript/function.scm:40:9: warning: possibly unbound variable `<js-array-object>'
language/ecmascript/function.scm:44:43: warning: possibly unbound variable `js-array-vector'
system/repl/debug.scm:172:24: warning: possibly unbound variable `program-module'
system/repl/server.scm:68:41: warning: possibly unbound variable `inet-aton'
5. "warning: pointer targets in passing argument" in make
srfi-4.c:156:1: warning: pointer targets in passing argument 1 of 'scm_c_take_typed_bytevector' differ in signedness [-Wpointer-sign]
srfi-4.c:159:1: warning: pointer targets in passing argument 1 of 'scm_c_take_typed_bytevector' differ in signedness [-Wpointer-sign]
srfi-4.c:162:1: warning: pointer targets in passing argument 1 of 'scm_c_take_typed_bytevector' differ in signedness [-Wpointer-sign]
srfi-4.c:165:1: warning: pointer targets in passing argument 1 of 'scm_c_take_typed_bytevector' differ in signedness [-Wpointer-sign]
srfi-4.c:168:1: warning: pointer targets in passing argument 1 of 'scm_c_take_typed_bytevector' differ in signedness [-Wpointer-sign]
srfi-4.c:171:1: warning: pointer targets in passing argument 1 of 'scm_c_take_typed_bytevector' differ in signedness [-Wpointer-sign]
srfi-4.c:174:1: warning: pointer targets in passing argument 1 of 'scm_c_take_typed_bytevector' differ in signedness [-Wpointer-sign]
srfi-4.c:177:1: warning: pointer targets in passing argument 1 of 'scm_c_take_typed_bytevector' differ in signedness [-Wpointer-sign]
srfi-4.c:180:1: warning: pointer targets in passing argument 1 of 'scm_c_take_typed_bytevector' differ in signedness [-Wpointer-sign]
srfi-4.c:183:1: warning: pointer targets in passing argument 1 of 'scm_c_take_typed_bytevector' differ in signedness [-Wpointer-sign]
srfi-4.c:189:1: warning: pointer targets in passing argument 1 of 'scm_c_take_typed_bytevector' differ in signedness [-Wpointer-sign]
srfi-4.c:192:1: warning: pointer targets in passing argument 1 of 'scm_c_take_typed_bytevector' differ in signedness [-Wpointer-sign]
6. "%% xxxxx/xxxxx conflict" in make
See attached file.
--- Kiyoshi <yoi_no_myoujou@yahoo.co.jp>
[-- Attachment #2: conflict.gz --]
[-- Type: application/x-tar, Size: 296 bytes --]
reply other threads:[~2016-01-31 22:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=175856.3892.qm@web101213.mail.kks.yahoo.co.jp \
--to=yoi_no_myoujou@yahoo.co.jp \
--cc=22509@debbugs.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).