Re: guile 1.8.3 compilation errors on AIX 6.1

[Neil Jerram]

Rainer Tammer <address@hidden> writes:

> Hello Neil,
> sorry to bother you again (and again)...

No problem; I'm sorry that Guile doesn't Just Work yet on AIX...

> 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

We have a pragmatic "fix" for this one already in CVS (and so will be
in 1.8.4); see here:
http://lists.gnu.org/archive/html/bug-guile/2008-01/msg00076.html

> There is also a problem in net_db.c
>
> hstrerror needs _USE_IRS defined on AIX otherwise you get a
> compilation error...

So how did HAVE_HSTRERROR manage to get defined during the ./configure
step?

> 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)

Not sure about these; I'll come back to them later.

> Running socket.test
> FATAL: memory error in realloc
> /usr/bin/bash: line 1: 393334 IOT/Abort trap          (core dumped)

Could you send us the last few lines of check-guile.log (in $TOPDIR);
that should indicate which of the cases in socket.test passed, before
the one that trapped.

Thanks,
        Neil