Re: [Chicken-users] Out-of-date arguments in some egg setups
On 7/17/05, Kon Lovett [EMAIL PROTECTED] wrote: postgresql.setup-hygienic rfc3339.setup -H srfi-42.setup -H srfi-57.setup -H test-infrastructure.setup -H utf8.setup -syntax These should be fixed by now (I actually updated them at the same time as 2.0 was uploaded). If you fetch/install them again, things should be fine. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Re: bug report: inexact-exact srfi-18
On 7/17/05, Kon Lovett [EMAIL PROTECTED] wrote: Using Chicken 2.0 # (require-extension srfi-18) ; loading library srfi-18 ... # (seconds-time 1) Here's a patch. Thanks! 120,121c120,121 (let* ([n2 (- n C_startup_time_seconds)] ; seconds since startup [ms (truncate (* 1000 (##sys#flonum-fraction n)))] ; milliseconds --- (let* ([n2 (max 0 (- n C_startup_time_seconds))] ; seconds since startup [ms (truncate (* 1000 (##sys#flonum-fraction (##sys#exact-inexact n] ; milliseconds cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] libffi in chicken-2.0
Hello all, I'm trying to build the new release with --with-libffi, but it appears that the configuration is messed up. (my compiler output is appended) Specifically, it seems that libffi is *not* compiled into libchicken, and so to use libchicken, libffi.a must be explicitly included when compiling any scheme(chicken) code (for use e.g. by C_apply()). Is this the desired behaviour? I couldn't find this documented anywhere. Also, it appears that the *config script* knows to use -lffi (try fgrep lffi * at top-level), but no one else does. BTW, congratulations on reaching 2.0! thanks, Daniel Faken --- dhcp4-41:~/chicken-2.0%make gmake all-am gmake[1]: Entering directory `/home/faken/chicken-2.0' /bin/sh ./libtool --mode=link gcc -I/home/faken/ffidl/libffi/include -L/home/faken/ffidl/libffi -export-dynamic -o nsample -static nsample.o libchicken.la -ldl -lm gcc -I/home/faken/ffidl/libffi/include -o nsample nsample.o -Wl,--export-dynamic -L/home/faken/ffidl/libffi ./.libs/libchicken.a -ldl -lm ./.libs/libchicken.a(libchicken_la-runtime.o)(.text+0x8fe9): In function `C_apply': : undefined reference to `ffi_type_pointer' ./.libs/libchicken.a(libchicken_la-runtime.o)(.text+0x8ff5): In function `C_apply': : undefined reference to `ffi_type_pointer' ./.libs/libchicken.a(libchicken_la-runtime.o)(.text+0x9001): In function `C_apply': : undefined reference to `ffi_type_pointer' ./.libs/libchicken.a(libchicken_la-runtime.o)(.text+0x9049): In function `C_apply': : undefined reference to `ffi_type_pointer' ./.libs/libchicken.a(libchicken_la-runtime.o)(.text+0x9087): In function `C_apply': : undefined reference to `ffi_type_void' ./.libs/libchicken.a(libchicken_la-runtime.o)(.text+0x9099): In function `C_apply': : undefined reference to `ffi_prep_cif' ./.libs/libchicken.a(libchicken_la-runtime.o)(.text+0x90d2): In function `C_apply': : undefined reference to `ffi_call' collect2: ld returned 1 exit status gmake[1]: *** [nsample] Error 1 ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] non-blocking (read)
For example, an application would be a server program that is controlable by a user through some kind of commands. In other words, a server program with CUI. Currently I could do it by csi, since it does not block the server thread, but what if I would like to compile it into a single executable? Would char-ready? help? Thanks, Daishi At Sun, 17 Jul 2005 09:01:48 +0200, felix winkelmann wrote: On 7/15/05, Daishi Kato [EMAIL PROTECTED] wrote: Hi, How could I make the standard (read) non-blocking? Sorry, but currently I/O from stdio and files is fully blocking. The reason why the REPL doesn't seem to block is due to a clever hack (originally by Chris Double) that performs a select(2) before actually reading an expression. Doing the same for every input would be too much and would slow down I/O unnecessarily (and Chicken's I/O isn't particularly fast in the first place). Do you have a particular application in mind? Perhaps we can find a workaround. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
