[Chicken-users] BUG, list-ref bug found in chicken version 4.7.0

2011-11-20 Thread 徐迪
Hello, I know this is not the right place to make a bug report, and I really don't know whether this is a bug. I did like the following: xudifsd@xudifsd-laptop:~$ csi #;1 (list-ref 2 '(1 5 2)) Segmentation fault xudifsd@xudifsd-laptop:~$ csi -v CHICKEN (c)2008-2011 The Chicken Team (c)2000-2007

Re: [Chicken-users] BUG, list-ref bug found in chicken version 4.7.0

2011-11-20 Thread Christian Kellermann
Hi, * xudi...@gmail.com [20 09:19]: Hello, I know this is not the right place to make a bug report, and I really don't know whether this is a bug. I did like the following: xudifsd@xudifsd-laptop:~$ csi #;1 (list-ref 2 '(1 5 2)) Segmentation fault xudifsd@xudifsd-laptop:~$ csi

[Chicken-users] Deployment test failure (latest sources, FreeBSD)

2011-11-20 Thread Vitaly Magerya
Hi, folks. While running gmake check the deployment test fails, saying: /libexec/ld-elf.so.1: Shared object libchicken.so.6 not found, required by rev-app The full log is at [1]. The chicken in question is bootstrapped using 4.7.0, and installed into /tmp/c0 (see the log for full

Re: [Chicken-users] BUG, list-ref bug found in chicken version 4.7.0

2011-11-20 Thread Blake Sweeney
Hi, Seems I forgot to send the last one to the whole list. On Sun, 20 Nov 2011 16:49:13 +0100, Christian Kellermann ck...@pestilenz.org wrote: Hi, * Blake Sweeney blakes...@gmail.com [20 16:26]: I've attached the output from chicken-bug. For reference I installed chicken with

[Chicken-users] Parallel build, again

2011-11-20 Thread Vitaly Magerya
Hi, folks. I'd like to bug you once again about the change to add support for parallel build (i.e. building chicken with gmake -j). We discussed this last month [3], but didn't reach any conclusion. This was also discussed in ticket 526 [2], which is still open. Anyway, the patch applicable to

Re: [Chicken-users] Deployment test failure (latest sources, FreeBSD)

2011-11-20 Thread Christian Kellermann
* Vitaly Magerya vmage...@gmail.com [20 17:40]: So, is this a known issue? If not, how do I diagnose it further? -deploy is known to be broken for NetBSD and OpenBSD. Does FreeBSD support the $ORIGIN setting for RPATH? Maybe this test should be skipped on BSDs... HTH, Christian -- Who

Re: [Chicken-users] Deployment test failure (latest sources, FreeBSD)

2011-11-20 Thread Vitaly Magerya
So, is this a known issue? If not, how do I diagnose it further? -deploy is known to be broken for NetBSD and OpenBSD. Does FreeBSD support the $ORIGIN setting for RPATH? It appears that it does, but you need to additionally pass -z origin to the linker. For example deploying like this seems

Re: [Chicken-users] Deployment test failure (latest sources, FreeBSD)

2011-11-20 Thread Vitaly Magerya
I wrote: Here's the test: rm -rf /rmp/cd mkdir -p /tmp/cd cd /tmp/cd Ugh, typo over there, it's /tmp/cd, not /rmp/cd. You have been warned. echo '(write 555)' | tee a.scm b.scm csc -deploy a.scm ldd a/a csc -deploy -L -z origin b.scm ldd b/b

Re: [Chicken-users] Deployment test failure (latest sources, FreeBSD)

2011-11-20 Thread Christian Kellermann
* Vitaly Magerya vmage...@gmail.com [20 19:26]: Actually, judging by the man pages [1-2] NetBSD and OpenBSD may require the same trick. This needs to be tested though. Here's the test: rm -rf /rmp/cd mkdir -p /tmp/cd cd /tmp/cd echo '(write 555)' | tee a.scm b.scm csc

Re: [Chicken-users] Deployment test failure (latest sources, FreeBSD)

2011-11-20 Thread Christian Kellermann
* Vitaly Magerya vmage...@gmail.com [20 19:26]: So, is this a known issue? If not, how do I diagnose it further? -deploy is known to be broken for NetBSD and OpenBSD. Does FreeBSD support the $ORIGIN setting for RPATH? It appears that it does, but you need to additionally pass -z

Re: [Chicken-users] Deployment test failure (latest sources, FreeBSD)

2011-11-20 Thread Vitaly Magerya
Christian Kellermann ck...@pestilenz.org wrote: I have also tried it with the attached patch, that should give the correct flags, maybe we are still missing something... Does the patch improve the situation for you? Indeed it does for me. Since it doesn't work for you on OpenBSD, I propose