guile-1.9.6 on Mac OS X

guile-1.9.6 on Mac OS X

[David Fang]

For guile-1.9.6:

The good news:
Compilation and tests pass on i686-apple-darwin10!
I've been preparing an experimental package for fink-users:
http://fink.cvs.sourceforge.net/viewvc/fink/experimental/fangism/finkinfo/

The bad news:
However on powerpc-apple-darwin8, the same process still fails (same issue 
I reported initially with 1.9.3 a few months ago):

ERROR: In procedure dynamic-func:
ERROR: dlsym(0x102a00, scm_init_r6rs_ports): symbol not found
FAIL: check-guile
==================================
1 of 1 test failed
Please report to bug-guile@gnu.org
==================================

I get this error even after removing other installed versions of guile and 
shared libraries, I'm still puzzled by this one.  I even tried running 
this test by hand, to no avail.

Fang

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

Re: guile-1.9.6 on Mac OS X

[David Fang]

Hi again, a little update on this matter:

> For guile-1.9.6:
>
> The good news:
> Compilation and tests pass on i686-apple-darwin10!
>
> The bad news:
> However on powerpc-apple-darwin8, the same process still fails (same issue I 
> reported initially with 1.9.3 a few months ago):
>
> Running r4rs.test
> Running r5rs_pitfall.test
> Running r6rs-ports.test
> ERROR: In procedure dynamic-func:
> ERROR: dlsym(0x102a00, scm_init_r6rs_ports): symbol not found
> FAIL: check-guile
> ==================================
> 1 of 1 test failed
> Please report to bug-guile@gnu.org
> ==================================
>
> I get this error even after removing other installed versions of guile and 
> shared libraries, I'm still puzzled by this one.  I even tried running this 
> test by hand, to no avail.

I found another version of (old guile 1.4) that I uninstalled before 
re-running the test, and this time the tests got further:

Running r6rs-ports.test
Running ramap.test
Running reader.test
Running receive.test
Running regexp.test
ERROR: regexp.test: regexp-quote: regexp/extended: (char 254 #\? "?" "?") 
- arguments: ((regular-expression-syntax "make-regexp" "empty 
(sub)expression" #f ("?")))
FAIL: regexp.test: regexp-quote: regexp/extended: (string "aX" 254 #\
....

(so regexp fails)

and eventually gets stuck on:

Running threads.test
<hangs for over a day (indefintely)>

pstree shows:
  | | |   \-+= 01236 fang make -k check
  | | |     \-+- 01246 fang /bin/sh -c fail= failcom='exit 1'; for f in x $MAKEF
  | | |       \-+- 04970 fang make check-am
  | | |         \-+- 05034 fang make check-TESTS
  | | |           \-+- 05044 fang /bin/sh -c failed=0; all=0; xfail=0; xpass=0;
  | | |             \-+- 05045 fang /Volumes/Mercedes2/sw/src/fink.build/guile19
  | | |               |--- 06065 fang (sh)
  | | |               |--- 06066 fang (sh)
  | | |               |--- 06067 fang (sh)
  | | |               |--- 06068 fang (sh)
  | | |               |--- 06071 fang (sh)
  | | |               |--- 06072 fang (sh)
  | | |               |--- 06073 fang (sh)
  | | |               |--- 06080 fang (cat)
  | | |               \--- 06081 fang (cat)

showing little or no activity in top.

What is this test supposed to do? any suggestions on debugging it?

Summary (powerpc-apple-darwin8):
1) regexp.test fails
2) threads.test hangs

Thanks for any help.

Fang

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

Re: guile-1.9.6 on Mac OS X

[David Fang]

>> The bad news: (powerpc-apple-darwin8)
>
> Running r6rs-ports.test
> Running ramap.test
> Running reader.test
> Running receive.test
> Running regexp.test
> ERROR: regexp.test: regexp-quote: regexp/extended: (char 254 #\? "?" "?") - 
> arguments: ((regular-expression-syntax "make-regexp" "empty (sub)expression" 
> #f ("?")))
> FAIL: regexp.test: regexp-quote: regexp/extended: (string "aX" 254 #\
> ....
>
> (so regexp fails)
>
> and eventually gets stuck on:
>
> Running threads.test
> <hangs for over a day (indefintely)>
>
> pstree shows:
> | | |   \-+= 01236 fang make -k check
> | | |     \-+- 01246 fang /bin/sh -c fail= failcom='exit 1'; for f in x 
> $MAKEF
> | | |       \-+- 04970 fang make check-am
> | | |         \-+- 05034 fang make check-TESTS
> | | |           \-+- 05044 fang /bin/sh -c failed=0; all=0; xfail=0; 
> xpass=0;
> | | |             \-+- 05045 fang 
> /Volumes/Mercedes2/sw/src/fink.build/guile19
> | | |               |--- 06065 fang (sh)
> | | |               |--- 06066 fang (sh)
> | | |               |--- 06067 fang (sh)
> | | |               |--- 06068 fang (sh)
> | | |               |--- 06071 fang (sh)
> | | |               |--- 06072 fang (sh)
> | | |               |--- 06073 fang (sh)
> | | |               |--- 06080 fang (cat)
> | | |               \--- 06081 fang (cat)
>
> showing little or no activity in top.
>
> What is this test supposed to do? any suggestions on debugging it?

I've run 'check-guile threads.test' by itself, and the check-guile.log 
shows:

PASS: threads.test: parallel: no forms
PASS: threads.test: parallel: 1
PASS: threads.test: parallel: 1 2
PASS: threads.test: parallel: 1 2 3
PASS: threads.test: n-par-for-each: 0 in limit 10
PASS: threads.test: n-par-for-each: 6 in limit 10
PASS: threads.test: n-par-for-each: 6 in limit 1
PASS: threads.test: n-par-for-each: 6 in limit 2
PASS: threads.test: n-par-for-each: 6 in limit 3
PASS: threads.test: n-for-each-par-map: asyncs are still working 2
PASS: threads.test: n-for-each-par-map: 0 in limit 10
PASS: threads.test: n-for-each-par-map: 6 in limit 10
PASS: threads.test: n-for-each-par-map: 6 in limit 1
PASS: threads.test: n-for-each-par-map: 6 in limit 2
PASS: threads.test: n-for-each-par-map: 6 in limit 3
PASS: threads.test: lock-mutex: asyncs are still working 3
PASS: threads.test: lock-mutex: timed locking fails if timeout exceeded
PASS: threads.test: lock-mutex: asyncs are still working 6
PASS: threads.test: lock-mutex: timed locking succeeds if mutex unlocked within timeout
PASS: threads.test: lock-mutex: asyncs are still working 7
PASS: threads.test: unlock-mutex: asyncs are still working 5
PASS: threads.test: unlock-mutex: timed unlocking returns #f if timeout exceeded
PASS: threads.test: unlock-mutex: asyncs are still working 4
PASS: threads.test: unlock-mutex: timed unlocking returns #t if condition signaled
PASS: threads.test: join-thread: timed joining fails if timeout exceeded
PASS: threads.test: join-thread: join-thread returns timeoutval on timeout
PASS: threads.test: join-thread: timed joining succeeds if thread exits within timeout
PASS: threads.test: join-thread: asyncs are still working 1
PASS: threads.test: join-thread: don't hang when joined thread terminates in SCM_TICK

So it seems to be hanging on the
(with-test-prefix "cancel-thread" ...) section.
Even the first sub-test (pass-if "cancel succeeds" ...) hangs 
indefinitely.

If I comment out that section for now, at least the tests finish, but 
with one more failure:

FAIL: threads.test: mutex-ownership: mutex with owner not retained (bug #27450)

Totals for this test run:
passes:                 40
failures:               1
unexpected passes:      0
expected failures:      0
unresolved test cases:  0
untested test cases:    0
unsupported test cases: 0
errors:                 0

I was informed on another mailing list that thread-cancellation might not 
be supported on darwin8:
http://mailman.videolan.org/pipermail/vlc-devel/2009-September/066428.html

If this is indeed the case, is there any hope for testing/supporting 
threads on powerpc-apple-darwin8?

> Summary (powerpc-apple-darwin8):
> 1) regexp.test fails
> 2) threads.test hangs - on thread cancellation section
>
> Thanks for any help.

Fang

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