unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Rainer Tammer <tammer@tammer.net>
To: ludo@gnu.org
Cc: bug-guile@gnu.org
Subject: Re: guile 1.6.8 make check failure on AIX 6.1
Date: Sat, 02 Feb 2008 13:12:29 +0100	[thread overview]
Message-ID: <47A45E2D.8080201@tammer.net> (raw)

Hello,
I am currently trying this. But unfortunately the compile fails...

gmake  all-recursive
gmake[1]: Entering directory `/daten/source/guile-1.8.3'
Making all in oop
gmake[2]: Entering directory `/daten/source/guile-1.8.3/oop'
Making all in goops
gmake[3]: Entering directory `/daten/source/guile-1.8.3/oop/goops'
gmake[3]: Nothing to be done for `all'.
gmake[3]: Leaving directory `/daten/source/guile-1.8.3/oop/goops'
gmake[3]: Entering directory `/daten/source/guile-1.8.3/oop'
gmake[3]: Nothing to be done for `all-am'.
gmake[3]: Leaving directory `/daten/source/guile-1.8.3/oop'
gmake[2]: Leaving directory `/daten/source/guile-1.8.3/oop'
Making all in libguile
gmake[2]: Entering directory `/daten/source/guile-1.8.3/libguile'
Generating libpath.h...
./guile-snarf -o load.x load.c -DHAVE_CONFIG_H -I.. -I.. 
-I/opt/freeware/include -g -O2 -Wall -Wmissing-prototypes -
Werror
gmake  all-am
gmake[3]: Entering directory `/daten/source/guile-1.8.3/libguile'
/usr/bin/bash ../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H 
-I. -I.. -I.. -I..  -I/opt/freeware/include -
D_THREAD_SAFE  -g -O2 -Wall -Wmissing-prototypes -Werror -MT 
libguile_la-discouraged.lo -MD -MP -MF .deps/libguile_l
a-discouraged.Tpo -c -o libguile_la-discouraged.lo `test -f 
'discouraged.c' || echo './'`discouraged.c
 gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I/opt/freeware/include 
-D_THREAD_SAFE -g -O2 -Wall -Wmissing-prototypes -We
rror -MT libguile_la-discouraged.lo -MD -MP -MF 
.deps/libguile_la-discouraged.Tpo -c discouraged.c  -DPIC -o .libs/l
ibguile_la-discouraged.o
In file included from ../libguile/gc.h:27,
                 from ../libguile.h:73,
                 from discouraged.c:22:
../libguile/hooks.h:43: error: expected ';', ',' or ')' before '.' token
../libguile/hooks.h:48: error: expected specifier-qualifier-list before 
'scm_t_c_hook_function'
../libguile/hooks.h:62: error: expected declaration specifiers or '...' 
before 'scm_t_c_hook_function'
../libguile/hooks.h:63: error: expected ';', ',' or ')' before '.' token
../libguile/hooks.h:66: error: expected declaration specifiers or '...' 
before 'scm_t_c_hook_function'
../libguile/hooks.h:67: error: expected ';', ',' or ')' before '.' token
gmake[3]: *** [libguile_la-discouraged.lo] Error 1
gmake[3]: Leaving directory `/daten/source/guile-1.8.3/libguile'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory `/daten/source/guile-1.8.3/libguile'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/daten/source/guile-1.8.3'
gmake: *** [all] Error 2

I will try to find the problem.

The following is true for both guile 1.6.x and 1.8.x:

The build tools used (config.guess, libtool, autoconf) are to old for 
AIX 6.1.
With the old tools it is not possible to build a shared version.

I managed to build a shared version of guile 1.6.8 witch passes the 
shared test but which fails the srfi-4.test test (please see last post 
to the list).

-------- errors ---------
Running srfi-4.test
ERROR: srfi-4.test: u8 vector: u8vector? success - arguments: 
((memory-allocation-error "make-u8vector" "Memory allocation error" #f #f))
ERROR: srfi-4.test: u8 vector: u8vector-length success 1 - arguments: 
((memory-allocation-error "list->u8vector" "Memory allocation error" #f #f))
ERROR: srfi-4.test: s8 vector: s8vector? success - arguments: 
((memory-allocation-error "make-s8vector" "Memory allocation error" #f #f))
ERROR: srfi-4.test: s8 vector: s8vector-length success 1 - arguments: 
((memory-allocation-error "list->s8vector" "Memory allocation error" #f #f))
ERROR: srfi-4.test: u16 vector: u16vector? success - arguments: 
((memory-allocation-error "make-u16vector" "Memory allocation error" #f #f))
ERROR: srfi-4.test: u16 vector: u16vector-length success 1 - arguments: 
((memory-allocation-error "list->u16vector" "Memory allocation error" #f 
#f))
ERROR: srfi-4.test: s16 vector: s16vector? success - arguments: 
((memory-allocation-error "make-s16vector" "Memory allocation error" #f #f))
ERROR: srfi-4.test: s16 vector: s16vector-length success 1 - arguments: 
((memory-allocation-error "list->s16vector" "Memory allocation error" #f 
#f))
ERROR: srfi-4.test: u32 vector: u32vector? success - arguments: 
((memory-allocation-error "make-u32vector" "Memory allocation error" #f #f))
ERROR: srfi-4.test: u32 vector: u32vector-length success 1 - arguments: 
((memory-allocation-error "list->u32vector" "Memory allocation error" #f 
#f))
ERROR: srfi-4.test: s32 vector: s32vector? success - arguments: 
((memory-allocation-error "make-s32vector" "Memory allocation error" #f #f))
ERROR: srfi-4.test: s32 vector: s32vector-length success 1 - arguments: 
((memory-allocation-error "list->s32vector" "Memory allocation error" #f 
#f))
ERROR: srfi-4.test: u64 vector: u64vector? success - arguments: 
((memory-allocation-error "make-u64vector" "Memory allocation error" #f #f))
ERROR: srfi-4.test: u64 vector: u64vector-length success 1 - arguments: 
((memory-allocation-error "list->u64vector" "Memory allocation error" #f 
#f))
ERROR: srfi-4.test: s64 vector: s64vector? success - arguments: 
((memory-allocation-error "make-s64vector" "Memory allocation error" #f #f))
ERROR: srfi-4.test: s64 vector: s64vector-length success 1 - arguments: 
((memory-allocation-error "list->s64vector" "Memory allocation error" #f 
#f))
ERROR: srfi-4.test: f32 vector: f32vector? success - arguments: 
((memory-allocation-error "make-f32vector" "Memory allocation error" #f #f))
ERROR: srfi-4.test: f32 vector: f32vector-length success 1 - arguments: 
((memory-allocation-error "list->f32vector" "Memory allocation error" #f 
#f))
ERROR: srfi-4.test: f64 vector: f64vector? success - arguments: 
((memory-allocation-error "make-f64vector" "Memory allocation error" #f #f))
ERROR: srfi-4.test: f64 vector: f64vector-length success 1 - arguments: 
((memory-allocation-error "list->f64vector" "Memory allocation error" #f 
#f))

-------- errors ---------

For the build tools I have used the following versions:

* config.guess: GNU config.guess (2008-01-07)
* libtool:  libtool --version / ltmain.sh (GNU libtool) 1.5.25a 
(1.1220.2.481 2008/01/12 13:58:43)
* manual patch to configure; add aix6* after each aix5* -> I did not 
want to regenerated the whole thing with the new autoconf

Bye
  Rainer




             reply	other threads:[~2008-02-02 12:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-02 12:12 Rainer Tammer [this message]
2008-02-03 23:51 ` guile 1.6.8 make check failure on AIX 6.1 Neil Jerram
2008-02-04  7:40   ` Rainer Tammer
2008-02-04  8:31     ` Rainer Tammer
2008-02-04  9:03     ` guile 1.8.3 compilation errors " Rainer Tammer
2008-02-06  0:00       ` Neil Jerram
2008-02-06  8:22         ` Rainer Tammer
  -- strict thread matches above, loose matches on Subject: below --
2008-01-31  9:34 guile 1.6.8 make check failure " Rainer Tammer
2008-02-01 10:45 ` Ludovic Courtès
2008-02-01 20:32 ` Neil Jerram
2008-02-02 11:31   ` Rainer Tammer
2008-02-03 23:47     ` Neil Jerram
2008-02-04  7:21       ` Rainer Tammer
2008-02-05 23:38         ` Neil Jerram
2008-02-04  9:02           ` Ludovic Courtès
2008-02-06 22:05             ` 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=47A45E2D.8080201@tammer.net \
    --to=tammer@tammer.net \
    --cc=bug-guile@gnu.org \
    --cc=ludo@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).