Re: debugging guile test failure and segfault.

2007-06-13 Thread Ludovic Courtès
Hey, <[EMAIL PROTECTED]> writes: > And keep the old behavior if pkgconfig isn't installed? I did not have that in mind, but why not: `guile-config' is a Guile script and it's sufficiently flexible for this I suppose. Thanks, Ludo'. ___ Guile-user m

Re: debugging guile test failure and segfault.

2007-06-13 Thread dsmich
"Ludovic Courtès" <[EMAIL PROTECTED]> wrote: > Hi, > > Greg Troxel <[EMAIL PROTECTED]> writes: > > > I have this patch lying around from adding pkgconfig support long ago; I > > think I sent it and there wasn't much interest then. > > FWIW, I'm all in favor of applying such a patch. We c

Re: debugging guile test failure and segfault.

2007-06-13 Thread Ludovic Courtès
Hi, Greg Troxel <[EMAIL PROTECTED]> writes: > I have this patch lying around from adding pkgconfig support long ago; I > think I sent it and there wasn't much interest then. FWIW, I'm all in favor of applying such a patch. We could keep `guile-config' for compatibility and have it invoke `pkg-c

Re: debugging guile test failure and segfault.

2007-06-13 Thread Greg Troxel
I have this patch lying around from adding pkgconfig support long ago; I think I sent it and there wasn't much interest then. Index: Makefile.am === RCS file: /QUIST-CVS/guile/Makefile.am,v retrieving revision 1.1.1.3 diff -u -r1.1.

Re: debugging guile test failure and segfault.

2007-06-13 Thread Greg Troxel
[EMAIL PROTECTED] (Ludovic Courtès) writes: > Greg Troxel <[EMAIL PROTECTED]> writes: > >> I think guile should have a .pc file for pkg-config and guile-config >> should be deprecated eventually. That's really orthogonal. > > Yeah, that's probably the way to go. It's also more > cross-compilati

Re: debugging guile test failure and segfault.

2007-06-13 Thread Andy Wingo
Hi Greg, On Sun, 2007-06-10 at 13:46 -0400, Greg Troxel wrote: > There are several ways that programs find shared libraries at runtime. > Some of my info is old, so sorry if I am incorrect: > > debian way: -rpath is evil. all libs are in /usr/lib, or use ld.so.conf > or ldconfig of some kind >

Re: debugging guile test failure and segfault.

2007-06-12 Thread Ludovic Courtès
Hi, Greg Troxel <[EMAIL PROTECTED]> writes: > I think guile should have a .pc file for pkg-config and guile-config > should be deprecated eventually. That's really orthogonal. Yeah, that's probably the way to go. It's also more cross-compilation-friendly I think. Thanks, Ludovic. _

Re: debugging guile test failure and segfault.

2007-06-12 Thread Greg Troxel
[EMAIL PROTECTED] (Ludovic Courtès) writes: > Dan McMahill <[EMAIL PROTECTED]> writes: > >> With that I don't have to modify the guile-config output. In other >> words by default I might just get "-L/my/guile/path/lib" where I may >> actually want "-L/my/guile/path/lib -Wl,-R/my/guile/path/lib".

Re: debugging guile test failure and segfault.

2007-06-11 Thread Dan McMahill
Ludovic Courtès wrote: Hi, Dan McMahill <[EMAIL PROTECTED]> writes: I'll bet thats whats going on with NetBSD as well. My failed tests are all inside a chroot environment. Well, we *could* modify the file port write (i.e., `fport_print ()') so that it doesn't fail when `ttyname' does, if th

Re: debugging guile test failure and segfault.

2007-06-11 Thread Ludovic Courtès
Hi, Dan McMahill <[EMAIL PROTECTED]> writes: > With that I don't have to modify the guile-config output. In other > words by default I might just get "-L/my/guile/path/lib" where I may > actually want "-L/my/guile/path/lib -Wl,-R/my/guile/path/lib". Greg Troxel <[EMAIL PROTECTED]> writes: > Pr

Re: debugging guile test failure and segfault.

2007-06-11 Thread Ludovic Courtès
[EMAIL PROTECTED] (Ludovic Courtès) writes: > Well, we *could* modify the file port write (i.e., `fport_print ()') so > that it doesn't fail when `ttyname' does, if that's a common problem. > > Or you could set up a chroot jail where `/dev/pts/*' are visible, if > that's the source of the problem.

Re: debugging guile test failure and segfault.

2007-06-11 Thread Ludovic Courtès
Hi, Dan McMahill <[EMAIL PROTECTED]> writes: > I'll bet thats whats going on with NetBSD as well. My failed tests > are all inside a chroot environment. Well, we *could* modify the file port write (i.e., `fport_print ()') so that it doesn't fail when `ttyname' does, if that's a common problem.

Re: debugging guile test failure and segfault.

2007-06-10 Thread Greg Troxel
[EMAIL PROTECTED] (Ludovic Courtès) writes: >> --- guile-config/guile-config.in.orig 2006-09-20 00:19:02.0 + >> +++ guile-config/guile-config.in >> @@ -155,7 +155,7 @@ >> (if (or (string=? libdir "/usr/lib") >> (string=? libdir "/usr/lib/")) >

Re: debugging guile test failure and segfault.

2007-06-10 Thread Dan McMahill
Ludovic Courtès wrote: Hi, Dan McMahill <[EMAIL PROTECTED]> writes: Backtrace: In unknown file: ?: 0* [primitive-load "test-suite/tests/r4rs.test"] In test-suite/tests/r4rs.test: 923: 1* Exception during displaying of backtrace: system-error test-suite/tests/r4rs.test:88:45: In procedure

Re: debugging guile test failure and segfault.

2007-06-10 Thread Dan McMahill
Ludovic Courtès wrote: Hi, Dan McMahill <[EMAIL PROTECTED]> writes: I'm also working on getting this going on Solaris-2.9/sparc but am not quite to the testsuite part. I have a few bug fix patches there too. Once I get my various problems worked out, I'll submit a more cleaned up set of patch

Re: debugging guile test failure and segfault.

2007-06-10 Thread Ludovic Courtès
Hi, Dan McMahill <[EMAIL PROTECTED]> writes: > Backtrace: > In unknown file: >?: 0* [primitive-load "test-suite/tests/r4rs.test"] > In test-suite/tests/r4rs.test: > 923: 1* > Exception during displaying of backtrace: system-error > > test-suite/tests/r4rs.test:88:45: In procedure ttyname in

Re: debugging guile test failure and segfault.

2007-06-10 Thread Ludovic Courtès
Hi, Dan McMahill <[EMAIL PROTECTED]> writes: >>> I'm also working on getting this going on Solaris-2.9/sparc but am not >>> quite to the testsuite part. I have a few bug fix patches there >>> too. Once I get my various problems worked out, I'll submit a more >>> cleaned up set of patches. > > se

Re: debugging guile test failure and segfault.

2007-06-09 Thread Dan McMahill
I'm also working on getting this going on Solaris-2.9/sparc but am not quite to the testsuite part. I have a few bug fix patches there too. Once I get my various problems worked out, I'll submit a more cleaned up set of patches. see the attached file for most of my patches. One I didn't includ

Re: debugging guile test failure and segfault.

2007-06-08 Thread Dan McMahill
Ludovic Courtès wrote: Hi, Dan McMahill <[EMAIL PROTECTED]> writes: a back trace showed that around line 834 of libguile/posix.c there is a call to ttyname() which is returning NULL. Unfortunately that NULL pointer is used a few lines later by some functions which try to run strlen() on it.

Re: debugging guile test failure and segfault.

2007-06-07 Thread Ludovic Courtès
Hi, Dan McMahill <[EMAIL PROTECTED]> writes: > a back trace showed that around line 834 of libguile/posix.c there is > a call to ttyname() which is returning NULL. Unfortunately that NULL > pointer is used a few lines later by some functions which try to run > strlen() on it. Thats where the s

Re: debugging guile test failure and segfault.

2007-06-06 Thread Dan McMahill
Ludovic Courtès wrote: Hi, Dan McMahill <[EMAIL PROTECTED]> writes: Running r4rs.test [1] Segmentation fault ${dir}${tst} FAIL: check-guile I guess you'll have to send us a stack trace. :-) So you need to make sure you compile Guile with the `-g' flags (e.g., by running "make CFL

Re: debugging guile test failure and segfault.

2007-06-06 Thread Ludovic Courtès
Hi, Dan McMahill <[EMAIL PROTECTED]> writes: > Running numbers.test > FAIL: numbers.test: max: big / real: (= big*5 (max big*5 -inf.0)) > FAIL: numbers.test: max: real / big: (= big*5 (max -inf.0 big*5)) > FAIL: numbers.test: min: big / real: (= big*5 (min big*5 +inf.0)) > FAIL: numbers.test: min

debugging guile test failure and segfault.

2007-06-04 Thread Dan McMahill
Hello, I've managed to get guile-1.8.1 to build (with a few patches) on my NetBSD/alpha system. Now I'm trying to investigate some failing tests. The tests which fail are: Running numbers.test FAIL: numbers.test: max: big / real: (= big*5 (max big*5 -inf.0)) FAIL: numbers.test: max: real /