[Chicken-users] gethostbyname() is deprecated in favour of getaddrinfo()

2014-10-02 Thread Moritz Wilhelmy
Dear Chickeneers, While building the OpenSuSE package for Chicken, I discovered the following: [ 473s] RPMLINT report: [ 473s] === [ 482s] chicken-runtime.i586: I: binary-or-shlib-calls-gethostbyname /usr/lib/libchicken.so.7 [ 482s] The binary calls gethostbyname(). Please port

Re: [Chicken-users] pressed Ctrl-\ and got segmentation fault

2013-06-23 Thread Moritz Wilhelmy
On 21.06.2013 22:34, John Cowan wrote: I can confirm that on 32-bit Linux. On Cygwin, however, typing ^\ does trigger a SIGSEGV with dumped core (except that it doesn't actually dump core because the Windows kernel can't do that). Both systems are running version 4.8.2 (rev ea02c9a), and

Re: [Chicken-users] pressed Ctrl-\ and got segmentation fault

2013-06-21 Thread Moritz Wilhelmy
Hello, On Tue, Jun 18, 2013 at 09:36:43 +0200, Peter Bex wrote: On Tue, Jun 18, 2013 at 12:02:56AM -0500, Daniel Ajoy wrote: This is my .csirc (use readline irregex) (current-input-port (make-gnu-readline-port)) (gnu-readline-parse-and-bind set editing-mode vi)

Re: [Chicken-users] pressed Ctrl-\ and got segmentation fault

2013-06-21 Thread Moritz Wilhelmy
Hello Daniel, On Fri, Jun 21, 2013 at 10:54:53 +0200, Moritz Wilhelmy wrote: I can confirm that it happens without any readline-ish extensions (and in fact no ~/.csirc at all). This chicken 4.7.0 is on FreeBSD/amd64 9.1-RELEASE. It should be noted that ^\ sends SIGQUIT, similar to the way ^C

Re: [Chicken-users] A fix for parallel build (gmake -j)

2011-10-06 Thread Moritz Wilhelmy
On Thu, Oct 06, 2011 at 15:37:08 +0300, Vitaly Magerya wrote: --- rules.make.orig 2011-10-06 14:50:00.0 +0300 +++ rules.make2011-10-06 14:50:06.0 +0300 @@ -242,7 +242,7 @@ # import libraries and extensions -%.so: %.o +%.so: %.o $(PRIMARY_LIBCHICKEN)

Re: [Chicken-users] Stupid questions regarding the mbox egg

2011-09-07 Thread Moritz Wilhelmy
Hi Ivan, On Tue, Sep 06, 2011 at 22:08:30 +0900, Ivan Raikov wrote: Thanks for using the mbox library. The documentation was not up-to-date, which has been fixed now. wow, you're fast :-) Some time ago, I generalized the parsing procedures of mbox so that they can take different types of

[Chicken-users] type problem with mbox egg

2011-09-05 Thread Moritz Wilhelmy
Hello, I have following problem with the mbox egg: Invoking mbox-file-messages always gives me a call of non-procedure error. #;5 (mbox-file-messages foo) Error: call of non-procedure: foo Call history: syntax (mbox-file-messages foo) eval