From: Rainer Tammer <tammer@tammer.net>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: bug-guile@gnu.org
Subject: Re: guile 1.6.8 make check failure on AIX 6.1
Date: Sat, 02 Feb 2008 12:31:07 +0100 [thread overview]
Message-ID: <47A4547B.8020206@tammer.net> (raw)
In-Reply-To: <87ejbwifjj.fsf@ossau.uklinux.net>
[-- Attachment #1: Type: text/plain, Size: 6029 bytes --]
Hello,
Neil Jerram wrote:
[...]
>> ERROR: In procedure dynamic-link:
>> ERROR: file: "libguile-srfi-srfi-13-14-v-1", message: " 0509-022
>> Cannot load module
>> /opt/freeware/lib/gcc/powerpc-ibm-aix6.1.0.0/4.2.2/../../../libguile-srfi-srfi-13-14-v-1.a.
>> 0509-103 The module has an invalid magic number."
>>
>
> The test that fails is supposed to link with the not-yet-installed
> version of libguile-srfi-srfi-13-14-v-1 somewhere under
> /daten/source/guile-1.6.8/srfi, but it is actually picking up an
> already installed library under /opt/freeware/lib.
>
> Also, according to google, the invalid magic number message most often
> indicates a 32-bit/64-bit mixup. So perhaps the installed library is
> 64-bit, and the one you're trying to build is 32-bit.
>
> Anyway, it looks like you could solve the problem by somehow hiding
> the /opt/freeware/lib libraries when building Guile.
>
>
>> Bye
>> Rainer
>>
>
> Regards,
> Neil
>
>
>
I checked this build again and I think I have found the problem.
The build tools (libtool/autoconf/config.guess) used by guile 1.6.8 do
not support AIX 6.1
So the build of the shared libraries fail.
I have patched the configure scripts and I have refreshed libtool /
config.guess.
Now I have a different problem:
Testing /daten/source/guile-1.6.8/pre-inst-guile ...
with GUILE_LOAD_PATH=/daten/source/guile-1.6.8/test-suite
Running alist.test
Running and-let-star.test
Running bit-operations.test
Running c-api.test
Running chars.test
Running common-list.test
Running environments.test
Running eval.test
Running exceptions.test
Running filesys.test
Running format.test
Running gc.test
Running getopt-long.test
Running goops.test
Running guardians.test
Running hash.test
Running hooks.test
Running import.test
Running interp.test
Running list.test
Running load.test
Running numbers.test
Running optargs.test
Running poe.test
Running popen.test
Running ports.test
Running posix.test
Running r4rs.test
Running ramap.test
Running reader.test
Running receive.test
Running regexp.test
Running slib.test
Running srcprop.test
Running srfi-1.test
Running srfi-10.test
Running srfi-13.test
Running srfi-14.test
Running srfi-17.test
Running srfi-19.test
Running srfi-31.test
Running srfi-39.test
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))
Running srfi-9.test
Running strings.test
Running symbols.test
Running syncase.test
Running syntax.test
Running time.test
Running unif.test
Running version.test
Running weaks.test
Totals for this test run:
passes: 9738
failures: 0
unexpected passes: 0
expected failures: 18
unresolved test cases: 0
untested test cases: 0
unsupported test cases: 9
errors: 20
FAIL: check-guile
===================
1 of 1 tests failed
===================
If the build tools (config.guess, libtool, autoconf) are updated to
newer version than the shared library problem is gone.
I have used the latest config.guess + libtool-1.5-branch and I have
patched the two configure scripts to support AIX 6.1.
I have attached my build logs to this mail.
Any ideas ??
Bye
Rainer
[-- Attachment #2: build-loigs.zip --]
[-- Type: application/x-zip-compressed, Size: 61194 bytes --]
next prev parent reply other threads:[~2008-02-02 11:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 9:34 guile 1.6.8 make check failure on AIX 6.1 Rainer Tammer
2008-02-01 10:45 ` Ludovic Courtès
2008-02-01 20:32 ` Neil Jerram
2008-02-02 11:31 ` Rainer Tammer [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2008-02-02 12:12 Rainer Tammer
2008-02-03 23:51 ` Neil Jerram
2008-02-04 7:40 ` Rainer Tammer
2008-02-04 8:31 ` 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=47A4547B.8020206@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).