unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: David Fang <fang@csl.cornell.edu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: 1.9.3 check test fail (powerpc-apple-darwin8)
Date: Mon, 19 Oct 2009 16:29:12 -0400 (EDT)	[thread overview]
Message-ID: <20091019162731.U91989@shannon.csl.cornell.edu> (raw)
In-Reply-To: <20091016170632.V73353@shannon.csl.cornell.edu>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2456 bytes --]

I've re-confirmed my findings with guile-1.9.4.  Still stumped...

>>> I'm seeing the following check failure with guile-1.9.3 on
>>> powerpc-apple-darwin8 (plain ../configure, VPATH build):
>>> 
>>> ...
>>> Running r4rs.test
>>> Running r5rs_pitfall.test
>>> Running r6rs-ports.test
>>> ERROR: In procedure dynamic-func:
>>> ERROR: dlsym(0x103120, scm_init_r6rs_ports): symbol not found
>> 
>> The dlsym () call comes form module/rnrs/io/ports.scm:
>>  (load-extension "libguile" "scm_init_r6rs_ports")
>> The failure could mean that dlopen(3) didnt pick up the right libguile,
>> which normally shouldnt happen because the Libtool wrapper script at
>> libguile/guile sets up the right dynamic linker search path.
>> 
>> Can you try ./meta/guile -c '(use-modules (rnrs io ports))'?  If that
>> fails, can you try to somehow check what the dynamic linker search path
>> is? (I dont know how to do it on Mac OS X)
>
> Hi,
> 	Sorry for the delay.  I tried the pre-install meta/guile.
>
> 	$ (use-modules (rnrs io ports))
>
> This fails with the same dlsym error message, whether I run with -c, or 
> interactively. I checked the 'lsof' to see which libraries it is picking up 
> 'lsof -p PID', and it looks like it's picking up all shared libs in the build 
> directory properly:
>
> .../fink.build/guile19-1.9.3-1/guile-1.9.3/build/libguile/.libs/libguile.18.dylib
>
> % meta/guile
> $ (for-each (lambda (x) (display x) (newline)) %load-path )
> /Volumes/Mercedes2/sw/src/fink.build/guile19-1.9.3-1/guile-1.9.3/build/guile-readline
> /Volumes/Mercedes2/sw/src/fink.build/guile19-1.9.3-1/guile-1.9.3/guile-readline
> /Volumes/Mercedes2/sw/src/fink.build/guile19-1.9.3-1/guile-1.9.3/build
> /Volumes/Mercedes2/sw/src/fink.build/guile19-1.9.3-1/guile-1.9.3
> /Volumes/Mercedes2/sw/src/fink.build/guile19-1.9.3-1/guile-1.9.3/build/module
> /Volumes/Mercedes2/sw/src/fink.build/guile19-1.9.3-1/guile-1.9.3/module
> /sw/share/guile/site
> /sw/share/guile/1.9
> /sw/share/guile
>
> [/Volume/Mercedes2/sw/src/fink.build/... is where I'm building]
>
> I've checked that symbol table for 'nm libguile/.libs/libguile.dylib' 
> contains a defined symbol for "scm_init_r6rs_ports":
>
> 00061d60 T _scm_init_r6rs_ports
>
> Any other ideas?
>
> Fang
>
>
>
> David Fang
> http://www.csl.cornell.edu/~fang/
> http://www.achronix.com/
>

David Fang
http://www.csl.cornell.edu/~fang/
http://www.achronix.com/

      parent reply	other threads:[~2009-10-19 20:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-05  1:49 1.9.3 check test fail (powerpc-apple-darwin8) David Fang
2009-10-05  9:08 ` Ludovic Courtès
2009-10-16 21:18   ` David Fang
2009-10-19 16:44     ` Ludovic Courtès
2009-10-19 20:29     ` David Fang [this message]

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=20091019162731.U91989@shannon.csl.cornell.edu \
    --to=fang@csl.cornell.edu \
    --cc=guile-devel@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).