Re: [Chicken-users] Re: Sqlite3 Egg Installation Error
Instead of using Fink and a different path, I downloaded and compiled Sqlite3 directly and everything works perfectly. Thanks. On Sep 22, 2007, at 10:47 PM, Zbigniew wrote: When I had sqlite3 in a weird path, I used to pass this information to chicken-setup directly: e.g. chicken-setup -c "-I$HOME/local/include" -c "-L$HOME/local/lib" sqlite3 At other times, I built chicken itself with these -I and -L flags, so they would automatically be used by chicken-setup. As Thomas noted, the sqlite3 version included with OS X in /usr/lib is ancient version 3.1.3. I just build it from source and install in /usr/local/lib now. On 9/21/07, Thomas Christian Chust <[EMAIL PROTECTED]> wrote: I suggest that you edit the .setup file of the SQLite3 egg and add the appropriate library path to the compilation command. ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Slow unix-sockets?
On 20/09/2007, Peter Busser <[EMAIL PROTECTED]> wrote: > Is it possible that writing to/reading from UNIX domain sockets using the > unix-sockets egg is very very slow? > > When I connect the two programs using a normal UNIX pipe, then it takes > less than 0.6 seconds for a >100k message. But it takes more than 4 > seconds when I do the same over a UNIX domain socket. That is a difference > of a factor 8 or so. It runs on a 1G Pentium III machine. Has anyone of > you experienced this too? I wonder if you could give a small test program people could try in different environments? -- I appear to be temporarily using gmail's horrible interface. I apologise for any failure in my part in trying to make it do the right thing with post formatting. ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Help w/ PCRE 7.4 migration
Hallo, On 9/24/07, Kon Lovett <[EMAIL PROTECTED]> wrote: > > I need the "config.h" files produced by PCRE 7.4 (ftp:// > ftp.csx.cam.ac.uk/pub/software/programming/pcre/) 'configure --enable- > unicode-properties' from the following OS: > > Solaris 9 Sparc > > NetBDS PowerPC & x86-64 > > Linux PowerPC & x86-64 & x86 & Alpha & ARM/XScale > > (http://galinha.ucpel.tche.br/portability except for MacOS PowerPC & > Windows/MinGW32) > Attached there is the config file for Linux x86-64. Cheers, -- -alex http://www.ventonegro.org/ config.h Description: Binary data ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Imlib2 question
On 9/24/07, Peter Bex <[EMAIL PROTECTED]> wrote: > On Mon, Sep 24, 2007 at 04:29:25PM -0400, William Ramsay wrote: > > Why not just return a list and make it simple? I forgot to add this form, which "returns a list": (receive my-list (imlib:pixel/rgba img x y) (do-something-with my-list)) It doesn't really return a list, of course, but the pattern-match creates one for you. > I don't like > it one bit, precisely for this reason: it's damned confusing. I want > an error if I forgot to receive all values, I don't want the first > value, dammit! Personally, I find it useful. In this particular example, it makes less sense -- who wants the red-value without the other values as well? But there are useful cases for a "primary return value" with optional, secondary ones. > Complain to Felix about this if you don't like it :) You can if you wish, but I'll counter-complain. ;-) G ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] emacs editing mode for chicken ?
On 9/19/07, Tony Sidaway <[EMAIL PROTECTED]> wrote: > If you do use quack.el, you should perform the following edits: > > In ~/.emacs > > Add (load-file "~/quack.el") I think byte-compiling quack.el and putting: (require 'quack) would make things faster and more memory efficient. ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Imlib2 question
On Mon, Sep 24, 2007 at 10:42:22PM +0200, Peter Bex wrote: > Yes, this is (afaik) a deviation from the standard. I don't like > it one bit, precisely for this reason: it's damned confusing. I want > an error if I forgot to receive all values, I don't want the first > value, dammit! Sorry for the outburst... *blushes* :) Peter -- http://sjamaan.ath.cx -- "The process of preparing programs for a digital computer is especially attractive, not only because it can be economically and scientifically rewarding, but also because it can be an aesthetic experience much like composing poetry or music." -- Donald Knuth pgpV3aO4hNM2h.pgp Description: PGP signature ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Imlib2 question
On Mon, Sep 24, 2007 at 04:29:25PM -0400, William Ramsay wrote: > That's the problem, I don't know what to use.I've tried call-with-values > and receive, but both give me errors, mostly because I have no idea what > I'm doing.Receive expects (name1 name2 ...) valexp body, but this > produces an error since name1 is not a command. > > Why not just return a list and make it simple? Because the pixel routines conceptually return four values, _not_ one value which is a list. > The call to (imlib:pixel img x y) should return the r, g, b, a values > of the pixel. It should, and it does. > Just calling it produces r. Yes, this is (afaik) a deviation from the standard. I don't like it one bit, precisely for this reason: it's damned confusing. I want an error if I forgot to receive all values, I don't want the first value, dammit! (that's what it does; it discards all values except the first) Complain to Felix about this if you don't like it :) > The others are there, but how do I get them? (receive (r g b a) (imlib:pixel/rgba img x y) (do-something-with r g b a)) Alternatively, (call-with-values (lambda () (imlib:pixel/rgba img x y)) (lambda (r g b a) ...)) > confused Hope this helps! Cheers, Peter -- http://sjamaan.ath.cx -- "The process of preparing programs for a digital computer is especially attractive, not only because it can be economically and scientifically rewarding, but also because it can be an aesthetic experience much like composing poetry or music." -- Donald Knuth pgpdJYQlYalZe.pgp Description: PGP signature ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Imlib2 question
>On 9/24/07, William Ramsay <[EMAIL PROTECTED]> wrote: > That's the problem, I don't know what to use.I've tried call-with-values > and receive, but both give me errors, mostly because I have no idea what > I'm doing. > The call to (imlib:pixel img x y) should return the r, g, b, a values > of the pixel. Just calling it produces r. The others are there, but how > do I get them? I don't know imlib; but try: (receive (r g b a) (imlib:pixel img x y) (print "r is " r) (print "b is " b)) Graham ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Imlib2 question
That's the problem, I don't know what to use.I've tried call-with-values and receive, but both give me errors, mostly because I have no idea what I'm doing.Receive expects (name1 name2 ...) valexp body, but this produces an error since name1 is not a command. Why not just return a list and make it simple? The call to (imlib:pixel img x y) should return the r, g, b, a values of the pixel. Just calling it produces r. The others are there, but how do I get them? confused Alex Queiroz wrote: Hallo, On 9/24/07, William Ramsay <[EMAIL PROTECTED]> wrote: Hi, Can anyone explain to me how to get the four values from the imlib2 egg procedure (imlib:pixel/rgba img x y)? It seems to only return the first value, but it's supposed to return four values. This may be more of a scheme question than an imlib2 question, but either way I can't seem to get it to work. Are you using RECEIVE or LET-VALUES? Cheers, ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] tinyclos - how to copy an object?
On 9/21/07, Shawn Rutledge <[EMAIL PROTECTED]> wrote: > The indenting of let's you mean? Just a habit from C/C++... and it > makes inserting new ones easier. When I first started with Scheme I > used to line up all the parentheses but it got kindof "leggy". :-) Not an Emacs user? It's really worth the initial pain if you're writing much Scheme code. Emacs makes it a snap to navigate through sepxrs, reindent them, cut/copy/transpose them, etc. Paredit-mode for Emacs is a bonus, too; once I started using it, I never made another "parenthetical error". G ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Imlib2 question
Hallo, On 9/24/07, William Ramsay <[EMAIL PROTECTED]> wrote: > Hi, > > Can anyone explain to me how to get the four values from the imlib2 egg > procedure (imlib:pixel/rgba img x y)? It seems to only return the > first value, > but it's supposed to return four values. This may be more of a scheme > question than an imlib2 question, but either way I can't seem to get it > to work. > Are you using RECEIVE or LET-VALUES? Cheers, -- -alex http://www.ventonegro.org/ ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] Imlib2 question
Hi, Can anyone explain to me how to get the four values from the imlib2 egg procedure (imlib:pixel/rgba img x y)? It seems to only return the first value, but it's supposed to return four values. This may be more of a scheme question than an imlib2 question, but either way I can't seem to get it to work. What am I doing wrong? Bill ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Help w/ PCRE 7.4 migration
On Mon, Sep 24, 2007 at 07:05:24AM -0700, Kon Lovett wrote: > Hi all, > > I need the "config.h" files produced by PCRE 7.4 (ftp:// > ftp.csx.cam.ac.uk/pub/software/programming/pcre/) 'configure --enable- > unicode-properties' from the following OS: > > NetBDSPowerPC & x86-64 Here are the config.h files for NetBSD on both platforms. The macppc system is running NetBSD-4.0RC1 and the amd64 is running NetBSD-3.0 Peter -- http://sjamaan.ath.cx -- "The process of preparing programs for a digital computer is especially attractive, not only because it can be economically and scientifically rewarding, but also because it can be an aesthetic experience much like composing poetry or music." -- Donald Knuth /* config.h. Generated from config.h.in by configure. */ /* config.h.in. Generated from configure.ac by autoheader. */ /* On Unix-like systems config.h.in is converted by "configure" into config.h. Some other environments also support the use of "configure". PCRE is written in Standard C, but there are a few non-standard things it can cope with, allowing it to run on SunOS4 and other "close to standard" systems. If you are going to build PCRE "by hand" on a system without "configure" you should copy the distributed config.h.generic to config.h, and then set up the macro definitions the way you need them. You must then add -DHAVE_CONFIG_H to all of your compile commands, so that config.h is included at the start of every source. Alternatively, you can avoid editing by using -D on the compiler command line to set the macro values. In this case, you do not have to set -DHAVE_CONFIG_H. PCRE uses memmove() if HAVE_MEMMOVE is set to 1; otherwise it uses bcopy() if HAVE_BCOPY is set to 1. If your system has neither bcopy() nor memmove(), set them both to 0; an emulation function will be used. */ /* By default, the \R escape sequence matches any Unicode line ending character or sequence of characters. If BSR_ANYCRLF is defined, this is changed so that backslash-R matches only CR, LF, or CRLF. The build- time default can be overridden by the user of PCRE at runtime. On systems that support it, "configure" can be used to override the default. */ /* #undef BSR_ANYCRLF */ /* If you are compiling for a system that uses EBCDIC instead of ASCII character codes, define this macro as 1. On systems that can use "configure", this can be done via --enable-ebcdic. */ /* #undef EBCDIC */ /* Define to 1 if you have the `bcopy' function. */ #define HAVE_BCOPY 1 /* Define to 1 if you have the header file. */ #define HAVE_BITS_TYPE_TRAITS_H 1 /* Define to 1 if you have the header file. */ #define HAVE_DIRENT_H 1 /* Define to 1 if you have the header file. */ #define HAVE_DLFCN_H 1 /* Define to 1 if you have the header file. */ #define HAVE_INTTYPES_H 1 /* Define to 1 if you have the header file. */ #define HAVE_LIMITS_H 1 /* Define to 1 if the system has the type `long long'. */ #define HAVE_LONG_LONG 1 /* Define to 1 if you have the `memmove' function. */ #define HAVE_MEMMOVE 1 /* Define to 1 if you have the header file. */ #define HAVE_MEMORY_H 1 /* Define to 1 if you have the header file. */ #define HAVE_STDINT_H 1 /* Define to 1 if you have the header file. */ #define HAVE_STDLIB_H 1 /* Define to 1 if you have the `strerror' function. */ #define HAVE_STRERROR 1 /* Define to 1 if you have the header file. */ #define HAVE_STRING 1 /* Define to 1 if you have the header file. */ #define HAVE_STRINGS_H 1 /* Define to 1 if you have the header file. */ #define HAVE_STRING_H 1 /* Define to 1 if you have the `strtoll' function. */ #define HAVE_STRTOLL 1 /* Define to 1 if you have the `strtoq' function. */ #define HAVE_STRTOQ 1 /* Define to 1 if you have the header file. */ #define HAVE_SYS_STAT_H 1 /* Define to 1 if you have the header file. */ #define HAVE_SYS_TYPES_H 1 /* Define to 1 if you have the header file. */ /* #undef HAVE_TYPE_TRAITS_H */ /* Define to 1 if you have the header file. */ #define HAVE_UNISTD_H 1 /* Define to 1 if the system has the type `unsigned long long'. */ #define HAVE_UNSIGNED_LONG_LONG 1 /* Define to 1 if you have the header file. */ /* #undef HAVE_WINDOWS_H */ /* Define to 1 if you have the `_strtoi64' function. */ /* #undef HAVE__STRTOI64 */ /* The value of LINK_SIZE determines the number of bytes used to store links as offsets within the compiled regex. The default is 2, which allows for compiled patterns up to 64K long. This covers the vast majority of cases. However, PCRE can also be compiled to use 3 or 4 bytes instead. This allows for longer patterns in extreme cases. On systems that support it, "configure" can be used to override this default. */ #define LINK_SIZE 2 /* The value of MATCH_LIMIT determines the default number of times the internal match() function can be called during a single execution of pcre_exec(). There is a runtime
Re: [Chicken-users] Help w/ PCRE 7.4 migration
On 9/24/07, Kon Lovett <[EMAIL PROTECTED]> wrote: > I need the "config.h" files produced by PCRE 7.4 (ftp:// > ftp.csx.cam.ac.uk/pub/software/programming/pcre/) 'configure --enable- > unicode-properties' from the following OS: I've been meaning to add Solaris 10/SPARC to the "portability" list (a couple of tests to finish first); here's the config.h from that platform. Graham config.h Description: Binary data ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] Help w/ PCRE 7.4 migration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I need the "config.h" files produced by PCRE 7.4 (ftp:// ftp.csx.cam.ac.uk/pub/software/programming/pcre/) 'configure --enable- unicode-properties' from the following OS: Solaris 9 Sparc NetBDS PowerPC & x86-64 Linux PowerPC & x86-64 & x86 & Alpha & ARM/XScale (http://galinha.ucpel.tche.br/portability except for MacOS PowerPC & Windows/MinGW32) Thank you for your help, Kon -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iEYEARECAAYFAkb3xCUACgkQJJNoeGe+5O63YQCfQ/888btnkc7UbJi15ZBCLWeY zLkAnjRU04H9hIAEG/fWng6ykSr6mVDZ =dhhd -END PGP SIGNATURE- ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] -ldl problem
On 24 Sep 2007 08:34:32 -0300, Mario Domenech Goulart <[EMAIL PROTECTED]> wrote: > Hi > > On Mon, 24 Sep 2007 16:46:55 +0800 "naruto canada" <[EMAIL PROTECTED]> > wrote: > > > On 9/24/07, felix winkelmann <[EMAIL PROTECTED]> wrote: > > > On 9/18/07, naruto canada <[EMAIL PROTECTED]> wrote: > > > > > > > > my attemp to compile chicken scheme run into -ldl problem: > > > > ... > > > > ./libchicken.so: undefined reference to `dlerror' > > > > ./libchicken.so: undefined reference to `dlclose' > > > > ./libchicken.so: undefined reference to `dlopen' > > > > ./libchicken.so: undefined reference to `dlsym' > > > > ... > > > > > > > > This is how I solve it: > > > > sed -i "s/LIBRARIES =.*/LIBRARIES = -lm -ldl/" Makefile.linux > > > > make PLATFORM=linux PREFIX=/usr SYMBOLGC=1 > > > > make PLATFORM=linux PREFIX=/usr SYMBOLGC=1 install > > > > > > With what chicken version did you have this problem? > > > > chicken-2.709.tar.gz > > IIRC, 2.709 from 2007-09-18 had this bug. Can you try the most recent > snapshot (http://chicken.wiki.br/dev-snapshots/current)? chicken-2.711.tar.gz compiles clean on my system. thanks. > > Best wishes, > Mario > ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] -ldl problem
Hi On Mon, 24 Sep 2007 16:46:55 +0800 "naruto canada" <[EMAIL PROTECTED]> wrote: > On 9/24/07, felix winkelmann <[EMAIL PROTECTED]> wrote: > > On 9/18/07, naruto canada <[EMAIL PROTECTED]> wrote: > > > > > > my attemp to compile chicken scheme run into -ldl problem: > > > ... > > > ./libchicken.so: undefined reference to `dlerror' > > > ./libchicken.so: undefined reference to `dlclose' > > > ./libchicken.so: undefined reference to `dlopen' > > > ./libchicken.so: undefined reference to `dlsym' > > > ... > > > > > > This is how I solve it: > > > sed -i "s/LIBRARIES =.*/LIBRARIES = -lm -ldl/" Makefile.linux > > > make PLATFORM=linux PREFIX=/usr SYMBOLGC=1 > > > make PLATFORM=linux PREFIX=/usr SYMBOLGC=1 install > > > > With what chicken version did you have this problem? > > chicken-2.709.tar.gz IIRC, 2.709 from 2007-09-18 had this bug. Can you try the most recent snapshot (http://chicken.wiki.br/dev-snapshots/current)? Best wishes, Mario ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] -ldl problem
On 9/24/07, naruto canada <[EMAIL PROTECTED]> wrote: > On 9/24/07, felix winkelmann <[EMAIL PROTECTED]> wrote: > > On 9/18/07, naruto canada <[EMAIL PROTECTED]> wrote: > > > hi > > > > > > my attemp to compile chicken scheme run into -ldl problem: > > > ... > > > ./libchicken.so: undefined reference to `dlerror' > > > ./libchicken.so: undefined reference to `dlclose' > > > ./libchicken.so: undefined reference to `dlopen' > > > ./libchicken.so: undefined reference to `dlsym' > > > ... > > > > > > This is how I solve it: > > > sed -i "s/LIBRARIES =.*/LIBRARIES = -lm -ldl/" Makefile.linux > > > make PLATFORM=linux PREFIX=/usr SYMBOLGC=1 > > > make PLATFORM=linux PREFIX=/usr SYMBOLGC=1 install > > > > > > > Hi! > > > > > > With what chicken version did you have this problem? > > chicken-2.709.tar.gz > Thanks. This should be fixed in versions 2.710 and higher. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] -ldl problem
On 9/24/07, felix winkelmann <[EMAIL PROTECTED]> wrote: > On 9/18/07, naruto canada <[EMAIL PROTECTED]> wrote: > > hi > > > > my attemp to compile chicken scheme run into -ldl problem: > > ... > > ./libchicken.so: undefined reference to `dlerror' > > ./libchicken.so: undefined reference to `dlclose' > > ./libchicken.so: undefined reference to `dlopen' > > ./libchicken.so: undefined reference to `dlsym' > > ... > > > > This is how I solve it: > > sed -i "s/LIBRARIES =.*/LIBRARIES = -lm -ldl/" Makefile.linux > > make PLATFORM=linux PREFIX=/usr SYMBOLGC=1 > > make PLATFORM=linux PREFIX=/usr SYMBOLGC=1 install > > > > Hi! > > > With what chicken version did you have this problem? chicken-2.709.tar.gz > > > cheers, > felix > ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users