From: Rainer Tammer <tammer@tammer.net>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: bug-guile@gnu.org
Subject: Re: guile 1.8.3 compilation errors on AIX 6.1
Date: Mon, 04 Feb 2008 10:03:26 +0100 [thread overview]
Message-ID: <47A6D4DE.5090304@tammer.net> (raw)
In-Reply-To: <47A6C151.1020808@tammer.net>
Hello Neil,
sorry to bother you again (and again)...
There is also a problem in filesys.c
The function
#define FUNC_NAME s_scm_readdir
{
struct dirent_or_dirent64 *rdent;
[...]
declares "DIR *ds..." and later calls
SCM_SYSCALL (readdir_r_or_readdir64_r (ds, (struct dirent_or_dirent64
*) buf, &rdent));
The problem is that (at least AIX) expects DIR64 for ds...
=> readdir64_r uses DIR64
=> readdir_r uses DIR
There is also a problem in net_db.c
hstrerror needs _USE_IRS defined on AIX otherwise you get a compilation
error...
With this changes I can compile guile 1.8.3 on AIX 6.1.
check Result:
gmake check-TESTS
gmake[4]: Entering directory
`/daten/source/guile-1.8.3/test-suite/standalone'
PASS: test-system-cmds
PASS: test-require-extension
PASS: test-num2integral
PASS: test-round
PASS: test-gh
PASS: test-asmobs
PASS: test-list
PASS: test-unwind
PASS: test-conversion
PASS: test-use-srfi
===================
All 10 tests passed
===================
gmake check-TESTS
gmake[2]: Entering directory `/daten/source/guile-1.8.3'
Testing /daten/source/guile-1.8.3/pre-inst-guile ...
with GUILE_LOAD_PATH=/daten/source/guile-1.8.3/test-suite
Running alist.test
Running and-let-star.test
Running arbiters.test
Running bit-operations.test
Running c-api.test
Running chars.test
Running common-list.test
Running continuations.test
Running elisp.test
Running environments.test
Running eval.test
;;; (foo-pws)
UNRESOLVED: eval.test: promises: basic promise behaviour: a forced
promise does not reference its environm
ent
Running exceptions.test
Running filesys.test
Running format.test
Running fractions.test
Running ftw.test
Running gc.test
Running getopt-long.test
Running goops.test
Running guardians.test
UNRESOLVED: guardians.test: standard guardian functionality: guarding
independent objects: re-guarding non
-immediates
UNRESOLVED: guardians.test: standard guardian functionality: guarding
weakly referenced objects: guarded e
lement of weak vector gets eventually removed from weak vector
UNRESOLVED: guardians.test: standard guardian functionality: guarding
weak containers: element of guarded
weak vector gets collected
Running hash.test
Running hooks.test
Running import.test
Running interp.test
Running list.test
Running load.test
Running modules.test
Running numbers.test
FAIL: numbers.test: /: 1/complex: (/ 1e200+1e200i)
FAIL: numbers.test: exact->inexact: mantdig ones then 011..11, round
down: (64 332306998946228949779207691360534527 3.32306998946229e35):
pos: (= 3.32306998946229e35)
FAIL: numbers.test: exact->inexact: mantdig ones then 011..11, round
down: (64 332306998946228949779207691360534527 3.32306998946229e35):
neg: (= -3.32306998946229e35)
FAIL: numbers.test: exact->inexact: mantdig ones then 011..11, round
down: (65 664613997892457899558415382721069055 6.64613997892458e35):
pos: (= 6.64613997892458e35)
FAIL: numbers.test: exact->inexact: mantdig ones then 011..11, round
down: (65 664613997892457899558415382721069055 6.64613997892458e35):
neg: (= -6.64613997892458e35)
FAIL: numbers.test: exact->inexact: mantdig ones then 011..11, round
down: (66 1329227995784915799116830765442138111 1.32922799578492e36):
pos: (= 1.32922799578492e36)
FAIL: numbers.test: exact->inexact: mantdig ones then 011..11, round
down: (66 1329227995784915799116830765442138111 1.32922799578492e36):
neg: (= -1.32922799578492e36)
FAIL: numbers.test: exact->inexact: mantdig ones then 011..11, round
down: (67 2658455991569831598233661530884276223 2.65845599156983e36):
pos: (= 2.65845599156983e36)
FAIL: numbers.test: exact->inexact: mantdig ones then 011..11, round
down: (67 2658455991569831598233661530884276223 2.65845599156983e36):
neg: (= -2.65845599156983e36)
FAIL: numbers.test: exact->inexact: mantdig ones then 011..11, round
down: (68 5316911983139663196467323061768552447 5.31691198313966e36):
pos: (= 5.31691198313967e36)
[...]
Running optargs.test
Running options.test
Running poe.test
Running popen.test
Running ports.test
UNRESOLVED: ports.test: port-for-each: passing freed cell
Running posix.test
Running q.test
Running r4rs.test
Running r5rs_pitfall.test
Running ramap.test
Running reader.test
Running receive.test
Running regexp.test
Running socket.test
FATAL: memory error in realloc
/usr/bin/bash: line 1: 393334 IOT/Abort trap (core dumped)
${dir}$tst
FAIL: check-guile
==================================
1 of 1 tests failed
Please report to bug-guile@gnu.org
==================================
Bye
Rainer
next prev parent reply other threads:[~2008-02-04 9:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 12:12 guile 1.6.8 make check failure on AIX 6.1 Rainer Tammer
2008-02-03 23:51 ` Neil Jerram
2008-02-04 7:40 ` Rainer Tammer
2008-02-04 8:31 ` Rainer Tammer
2008-02-04 9:03 ` Rainer Tammer [this message]
2008-02-06 0:00 ` guile 1.8.3 compilation errors " Neil Jerram
2008-02-06 8:22 ` Rainer Tammer
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=47A6D4DE.5090304@tammer.net \
--to=tammer@tammer.net \
--cc=bug-guile@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).