Re: [Chicken-users] testing release candidate for 4.0.0
I'm trying it on the Mac (Leopard): /tmp [mini][12:18:32 AM] chicken-setup tinyclos dyld: lazy symbol binding failed: Symbol not found: _C_match_toplevel Referenced from: /usr/local/bin/chicken-setup Expected in: /usr/local/lib/libchicken.dylib dyld: Symbol not found: _C_match_toplevel Referenced from: /usr/local/bin/chicken-setup Expected in: /usr/local/lib/libchicken.dylib Trace/BPT trap csi works OK though. ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
On Sat, Mar 28, 2009 at 2:20 AM, Shawn Rutledge shawn.t.rutle...@gmail.com wrote: I'm trying it on the Mac (Leopard): [mini][12:18:32 AM] chicken-setup tinyclos chicken-setup doesn't exist in Chicken 4 (it's called chicken-install now), and tinyclos isn't packaged for Chicken 4 anyway. ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
On Sat, Mar 28, 2009 at 2:02 AM, Jim Ursetto zbignie...@gmail.com wrote: chicken-setup doesn't exist in Chicken 4 (it's called chicken-install now), and tinyclos isn't packaged for Chicken 4 anyway. Oh that would be why then. What's it going to take to get tinyclos on Chicken 4? ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
On Sat, Mar 28, 2009 at 9:25 PM, Shawn Rutledge shawn.t.rutle...@gmail.com wrote: On Sat, Mar 28, 2009 at 2:02 AM, Jim Ursetto zbignie...@gmail.com wrote: chicken-setup doesn't exist in Chicken 4 (it's called chicken-install now), and tinyclos isn't packaged for Chicken 4 anyway. Oh that would be why then. What's it going to take to get tinyclos on Chicken 4? I tried to port it, but ran into hard to debug (but possibly not overly dramatic) problems. Then I ran out of time for working more on it. It would be more worthwhile to write a CLOS-style object system from scratch - the chicken port was tuned so heavily (with too little result, alas), that it is too complex and very hard to understand. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
On Fri, Mar 27, 2009 at 4:28 PM, Leonardo Valeri Manera l.valeriman...@gmail.com wrote: I'm aware of that. The rest of the calls to the compiler are properly calling cl. Also, the MSVC makefile uses cat while the mingw and msys ones dont ... Yes, it also uses touch(1) somewhere. I'm going to test and fix the msvc build, but it will take a couple of days. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
Ok, admittedly its been ages since I've used MSVC on the commandline, but: make PLATFORM=msvc PREFIX=blah === (eventually) link -nologo -dll -implib:libchicken.lib \ -out:libchicken.dll library.obj eval.obj data-structures.obj ports.obj files.obj extras.obj lolevel.obj utils.obj tcp.obj srfi-1.obj srfi-4.obj srfi-13.obj srfi-14.obj srfi-18.obj srfi-69.obj posixwin.obj regex.obj scheduler.obj profiler.obj stub.obj expand.obj chicken-syntax.obj runtime.obj ws2_32.lib advapi32.lib link: invalid option -- n Try `link --help' for more information. make[1]: *** [libchicken.dll] Error 1 make[1]: Leaving directory `D:/software/Dev/Chicken/chicken-4.0.0' make: *** [all] Error 2 MSVC2k8, gnuwin32 make/utils. Leo ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
2009/3/27 Leonardo Valeri Manera l.valeriman...@gmail.com: Ok, admittedly its been ages since I've used MSVC on the commandline, but: make PLATFORM=msvc PREFIX=blah === (eventually) link -nologo -dll -implib:libchicken.lib \ -out:libchicken.dll library.obj eval.obj data-structures.obj ports.obj files.obj extras.obj lolevel.obj utils.obj tcp.obj srfi-1.obj srfi-4.obj srfi-13.obj srfi-14.obj srfi-18.obj srfi-69.obj posixwin.obj regex.obj scheduler.obj profiler.obj stub.obj expand.obj chicken-syntax.obj runtime.obj ws2_32.lib advapi32.lib link: invalid option -- n Try `link --help' for more information. make[1]: *** [libchicken.dll] Error 1 make[1]: Leaving directory `D:/software/Dev/Chicken/chicken-4.0.0' make: *** [all] Error 2 MSVC2k8, gnuwin32 make/utils. That's the GNU linker, not the msvc linker, I think. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
felix winkelmann scripsit: link -nologo -dll -implib:libchicken.lib \ -out:libchicken.dll library.obj eval.obj data-structures.obj ports.obj files.obj extras.obj lolevel.obj utils.obj tcp.obj srfi-1.obj srfi-4.obj srfi-13.obj srfi-14.obj srfi-18.obj srfi-69.obj posixwin.obj regex.obj scheduler.obj profiler.obj stub.obj expand.obj chicken-syntax.obj runtime.obj ws2_32.lib advapi32.lib link: invalid option -- n Try `link --help' for more information. That's the GNU linker, not the msvc linker, I think. It's neither: the GNU linker is called 'ld'. It's the GNU coreutils program 'link', which exposes the link() system call directly. So $PATH is screwed up, most likely. -- John Cowan co...@ccil.org http://www.ccil.org/~cowan Humpty Dump Dublin squeaks through his norse Humpty Dump Dublin hath a horrible vorse But for all his kinks English / And his irismanx brogues Humpty Dump Dublin's grandada of all rogues. --Cousin James ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
That's likely. The README mentions GNU make and other POSIX utilities and I just added the whole of GnuWin32 to the PATH. In that case, I have a couple of questions: 1) Exactly which POSIX Utilities are necessary? 2) Does it really need forward-slashes for PREFIX? Leo 2009/3/27 John Cowan co...@ccil.org: felix winkelmann scripsit: link -nologo -dll -implib:libchicken.lib \ -out:libchicken.dll library.obj eval.obj data-structures.obj ports.obj files.obj extras.obj lolevel.obj utils.obj tcp.obj srfi-1.obj srfi-4.obj srfi-13.obj srfi-14.obj srfi-18.obj srfi-69.obj posixwin.obj regex.obj scheduler.obj profiler.obj stub.obj expand.obj chicken-syntax.obj runtime.obj ws2_32.lib advapi32.lib link: invalid option -- n Try `link --help' for more information. That's the GNU linker, not the msvc linker, I think. It's neither: the GNU linker is called 'ld'. It's the GNU coreutils program 'link', which exposes the link() system call directly. So $PATH is screwed up, most likely. -- John Cowan co...@ccil.org http://www.ccil.org/~cowan Humpty Dump Dublin squeaks through his norse Humpty Dump Dublin hath a horrible vorse But for all his kinks English / And his irismanx brogues Humpty Dump Dublin's grandada of all rogues. --Cousin James ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
Ok, you need coreutils, but without link - for cat. Possibly you just need cat? So far so good, now it dies at: link -nologo chicken-bug.obj -out:chicken-bug.exe \ libchicken-static.lib ws2_32.lib advapi32.lib cc-c -o chicken.import.o chicken.import.c process_begin: CreateProcess(NULL, cc -c -o chicken.import.o chicken.import.c, ...) failed. make (e=2): The system cannot find the file specified. make[1]: *** [chicken.import.o] Error 2 make[1]: Leaving directory `D:/software/Dev/Chicken/chicken-4.0.0' make: *** [all] Error 2 Leo 2009/3/27 John Cowan co...@ccil.org: felix winkelmann scripsit: link -nologo -dll -implib:libchicken.lib \ -out:libchicken.dll library.obj eval.obj data-structures.obj ports.obj files.obj extras.obj lolevel.obj utils.obj tcp.obj srfi-1.obj srfi-4.obj srfi-13.obj srfi-14.obj srfi-18.obj srfi-69.obj posixwin.obj regex.obj scheduler.obj profiler.obj stub.obj expand.obj chicken-syntax.obj runtime.obj ws2_32.lib advapi32.lib link: invalid option -- n Try `link --help' for more information. That's the GNU linker, not the msvc linker, I think. It's neither: the GNU linker is called 'ld'. It's the GNU coreutils program 'link', which exposes the link() system call directly. So $PATH is screwed up, most likely. -- John Cowan co...@ccil.org http://www.ccil.org/~cowan Humpty Dump Dublin squeaks through his norse Humpty Dump Dublin hath a horrible vorse But for all his kinks English / And his irismanx brogues Humpty Dump Dublin's grandada of all rogues. --Cousin James ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
Hallo, On 3/27/09, Leonardo Valeri Manera l.valeriman...@gmail.com wrote: Ok, you need coreutils, but without link - for cat. Possibly you just need cat? So far so good, now it dies at: link -nologo chicken-bug.obj -out:chicken-bug.exe \ libchicken-static.lib ws2_32.lib advapi32.lib cc-c -o chicken.import.o chicken.import.c process_begin: CreateProcess(NULL, cc -c -o chicken.import.o chicken.import.c, ...) failed. make (e=2): The system cannot find the file specified. make[1]: *** [chicken.import.o] Error 2 make[1]: Leaving directory `D:/software/Dev/Chicken/chicken-4.0.0' make: *** [all] Error 2 The MS compiler is 'cl.exe'. -- -alex http://www.ventonegro.org/ ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
2009/3/25 Ivan Shcheklein shchekl...@gmail.com: Hi Felix, MSVC+Cygwin's tools. Build failed since both chichen-defaults and chicken-config contain something like this: I don't understand: MSVC + cygwin? cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
On Wed, Mar 25, 2009 at 10:11 PM, Elf e...@ephemeral.net wrote: no. what happened is that the quoting rules are screwed up. i forgot to backport the makefile from 3. ill do it in a few. Please don't touch it, unless we have figured out what exactly goes wrong. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
On Thu, Mar 26, 2009 at 4:24 AM, Taylor Venable tay...@metasyntax.net wrote: I get the following when running make fullcheck -- scripts/makedist.scm is not in the tarball. I should add it... Thanks. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
I don't give up that easily. Slapped a gnuwin32 install into the PATH, ran with backslashes, success! You learn something every day I guess, I never suspected MSYS-make would break when used outside of MSYS, though considering the PATH mangling MSYS does its not surprising at all. I'd feel daft, but instead I'll chalk it down to my being a taurus and barreling through problems horns-down. I'll give Mingw64 a whirl if that's even possible. Is it? ARCH=x86_64 with Mingw? Leo 2009/3/26 felix winkelmann bunny...@gmail.com: On Thu, Mar 26, 2009 at 12:55 PM, Leonardo Valeri Manera l.valeriman...@gmail.com wrote: Eh, I'll have to install make an other stuffs outside of MSYS' path then. Exactly what is required outside of GNU make? Calling msys make via absolute path unsurprisingly fails with the same errors. In any case, the README needs to be changed then, it says: - When installing under mingw, with a windows shell (cmd.exe), pass an absolute pathname as PREFIX and use forward slashes. TDM-mingw (gcc 4.3) (seems) to be working fine with MSYS. Ok, I guess it doesn't make sense then to try to emulate a non-MSYS mingw build. If the mingw-msys build works fine for you, you should use that one. Thanks for providing the infomation. I'll fix the README. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
On Thu, Mar 26, 2009 at 1:59 PM, Leonardo Valeri Manera l.valeriman...@gmail.com wrote: You learn something every day I guess, I never suspected MSYS-make would break when used outside of MSYS, though considering the PATH mangling MSYS does its not surprising at all. MSYS does many evil things. MSYS make also searches for suitable sh, I think. I can't follow anymore, there are too many MSYS-related options and setups. So, the situation is: - mingw-msys: you have mingw + msys - mingw: you *DON'T* have msys, just cmd.exe and bare bones mingw - msvc: *NO* mingw/msys, just GNU make and MSVC and cmd.exe Everything else is not supported. Have a nice day. I'll give Mingw64 a whirl if that's even possible. Is it? ARCH=x86_64 with Mingw? Oh boy - another combination of configuration options. Sure, try it out! cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
felix winkelmann scripsit: - mingw-msys: you have mingw + msys - mingw: you *DON'T* have msys, just cmd.exe and bare bones mingw I have never understood why we have both these builds, when it seems that mingw would suffice. It just means more documentation, more support, more stuff to convert at each release. -- John Cowan co...@ccil.org http://www.ccil.org/~cowan Does anybody want any flotsam? / I've gotsam. Does anybody want any jetsam? / I can getsam. --Ogden Nash, No Doctors Today, Thank You ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
On Thu, Mar 26, 2009 at 3:09 PM, John Cowan co...@ccil.org wrote: felix winkelmann scripsit: - mingw-msys: you have mingw + msys - mingw: you *DON'T* have msys, just cmd.exe and bare bones mingw I have never understood why we have both these builds, when it seems that mingw would suffice. It just means more documentation, more support, more stuff to convert at each release. mingw is a reasonable platform to develop on, if you want absolutely bare-bones support for chicken and are not interested in GNU tools. It's a build for Windows that only needs gcc and make. mingw-msys is for people who need basic GNU tools and sh (that would be me, for example). cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
So, MinGW64 build falls flat on its face after 3 lines. MinGW64 needs target and host set as 'x86_64-pc-mingw32'. This give you this commandline: make PLATFORM=mingw PREFIX=PREFIX ARCH=x86_64 HOSTSYSTEM=x86_64-pc-mingw32 TARGETSYSTEM=x86_64-pc-mingw32 Resulting in: make -f ./Makefile.mingw all make[1]: Entering directory `D:/software/Dev/Chicken/chicken-4.0.0' echo 0buildsvnrevision make[1]: *** No rule to make target `.\\apply-hack.x86_64.s', needed by `apply-hack.x86_64.o'. Stop. make[1]: Leaving directory `D:/software/Dev/Chicken/chicken-4.0.0' make: *** [all] Error 2 Am I the first person to try this? I feel positively pioneer-ish. Cheers, Leo 2009/3/26 felix winkelmann bunny...@gmail.com: I'll give Mingw64 a whirl if that's even possible. Is it? ARCH=x86_64 with Mingw? Oh boy - another combination of configuration options. Sure, try it out! cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
Leonardo Valeri Manera wrote: make PLATFORM=mingw PREFIX=PREFIX ARCH=x86_64 HOSTSYSTEM=x86_64-pc- mingw32 TARGETSYSTEM=x86_64-pc-mingw32 Try ARCH=x86-64 And move discussion to a new thread ;-) -Tobia ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
It was an experiment more than anything, I'll embark on this with any seriousity when 4 is actually released. Leo 2009/3/26 Tobia Conforto tobia.confo...@gmail.com: Leonardo Valeri Manera wrote: make PLATFORM=mingw PREFIX=PREFIX ARCH=x86_64 HOSTSYSTEM=x86_64-pc-mingw32 TARGETSYSTEM=x86_64-pc-mingw32 Try ARCH=x86-64 And move discussion to a new thread ;-) -Tobia ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
felix winkelmann scripsit: mingw-msys is for people who need basic GNU tools and sh (that would be me, for example). I understand why people would want to use msys. What I don't understand is what makes the plain mingw build so painful if you have msys too, such that we need a separate build for that case. -- There are three kinds of people in the world: John Cowan those who can count,co...@ccil.org and those who can't. ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
MSYS sh (and possibly the MSYS-* apps) do really convoluted quote, slash and path mangling to make sh on windows feel like sh on unix. Cheers, Leo 2009/3/26 John Cowan co...@ccil.org: felix winkelmann scripsit: mingw-msys is for people who need basic GNU tools and sh (that would be me, for example). I understand why people would want to use msys. What I don't understand is what makes the plain mingw build so painful if you have msys too, such that we need a separate build for that case. -- There are three kinds of people in the world: John Cowan those who can count, co...@ccil.org and those who can't. ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
Hallo, On Thu, Mar 26, 2009 at 4:50 PM, Leonardo Valeri Manera l.valeriman...@gmail.com wrote: MSYS sh (and possibly the MSYS-* apps) do really convoluted quote, slash and path mangling to make sh on windows feel like sh on unix. I guess the point is that you can build Chicken with MinGW + cmd.exe and use it inside MSYS without problems. Thus, no need for both makefiles. Cheers, -- -alex http://www.ventonegro.org/ ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
Hallo, [Putting chicken-users back...] On Thu, Mar 26, 2009 at 5:00 PM, Leonardo Valeri Manera l.valeriman...@gmail.com wrote: That's true, but you can't build chicken with mingw+cmd.exe using MSYS' make. As I found out today. It will hilariously fail to find basic stuff because its convinced the paths are different. I'm not sure what happens when you try to build eggs, but I'm sure that's another fertile breeding ground for hilarious failtrains. Anyways, on a completely different topic, it should build with all versions of MSVC ya? I'm gonna try 2k8 and 2k8+ICC11 tomorrow. Yes, you cannot. That's why you should use *MinGW*'s make. Cheers, -- -alex http://www.ventonegro.org/ ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
i have. look at the difference between the chicken3 branch and the other. the problem is that the msys environment is NOT the same as the mingw environment. period. msys is a fork of cygwin 1.3 (when it was still free) with the compilers kept mildly up to date with mingw. msys is a full build environment, though, and mingw installed in conjunction with msys will try using pieces of it all the time. mingw installed without msys uses windows paths, etc. the confusions here stem primarily from the poor explanations given in the mingw/msys documentation. it also explains why its fairly rare for devs to target both mingw and msys building :) bottom line: to test a mingw build, have a mingw installation without msys. to test a msys build, do a full mingw/msys installation. do not combine them, cause you will get peculiar behaviour. (this particular bug comes from using type (or cat) to try to read a file with shell redirects. it works fine in msys. in mingw its using cmd.exe, not bash.exe, and the behaviour is broken even for windows, so it gives a broken directory listing. you can see exactly where the break happens from where the slashes go from the front of each word to the back of each word (eg /a /b /foo bar/ c/ d/). this is not a problem in the chicken3 branch mingw makefile, as i had fixed it previously.) -elf On Thu, 26 Mar 2009, felix winkelmann wrote: On Wed, Mar 25, 2009 at 10:11 PM, Elf e...@ephemeral.net wrote: no. what happened is that the quoting rules are screwed up. i forgot to backport the makefile from 3. ill do it in a few. Please don't touch it, unless we have figured out what exactly goes wrong. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] testing release candidate for 4.0.0
Hi! The current release candidate can be found at: http://www.call-with-current-continuation.org/chicken-4.0.0.tar.gz I tested it on several systems (mingw(+msys), linux), but would appreciate if others could give it a try. Note that some minor recent trunk changes didn't make it, due to unclear portability. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
Hi Felix, MSVC+Cygwin's tools. Build failed since both chichen-defaults and chicken-config contain something like this: /backup /bin /cygdrive /cygwin.bat /cygwin.ico /dev /etc /home /lib /proc /tmp /usr /var generated benchmarks/ html/ scripts/ tests/ Is it expected? Seems that it's caused by echo commands without quotes, like: echo #define HAVE_INTTYPES_H 0 $@ The following works: echo #define HAVE_INTTYPES_H 0 $@ Ivan Shcheklein On Wed, Mar 25, 2009 at 6:31 PM, felix winkelmann bunny...@gmail.comwrote: Hi! The current release candidate can be found at: http://www.call-with-current-continuation.org/chicken-4.0.0.tar.gz I tested it on several systems (mingw(+msys), linux), but would appreciate if others could give it a try. Note that some minor recent trunk changes didn't make it, due to unclear portability. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
no. what happened is that the quoting rules are screwed up. i forgot to backport the makefile from 3. ill do it in a few. (youre seeing what happens when the 'cat' or 'type' goes horribly wrong. note how the slashes go from one side to the other.) -elf On Thu, 26 Mar 2009, Ivan Shcheklein wrote: Hi Felix, MSVC+Cygwin's tools. Build failed since both chichen-defaults and chicken-config contain something like this: /backup /bin /cygdrive /cygwin.bat /cygwin.ico /dev /etc /home /lib /proc /tmp /usr /var generated benchmarks/ html/ scripts/ tests/ Is it expected? Seems that it's caused by echo commands without quotes, like: echo #define HAVE_INTTYPES_H 0 $@ The following works: echo #define HAVE_INTTYPES_H 0 $@ Ivan Shcheklein On Wed, Mar 25, 2009 at 6:31 PM, felix winkelmann bunny...@gmail.comwrote: Hi! The current release candidate can be found at: http://www.call-with-current-continuation.org/chicken-4.0.0.tar.gz I tested it on several systems (mingw(+msys), linux), but would appreciate if others could give it a try. Note that some minor recent trunk changes didn't make it, due to unclear portability. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
Hi Felix On Wed, 25 Mar 2009 16:31:24 +0100 felix winkelmann bunny...@gmail.com wrote: The current release candidate can be found at: http://www.call-with-current-continuation.org/chicken-4.0.0.tar.gz I tested it on several systems (mingw(+msys), linux), but would appreciate if others could give it a try. Note that some minor recent trunk changes didn't make it, due to unclear portability. Great to see this rc for chicken 4. Thank you. I could compile and install it and a couple of eggs on Linux PPC: $ /usr/local/chicken-4.0.0/bin/csi -version CHICKEN (c)2008-2009 The Chicken Team (c)2000-2007 Felix L. Winkelmann Version 4.0.0 - SVN rev. 13887 linux-unix-gnu-ppc [ manyargs dload ptables applyhook ] compiled 2009-03-25 on mandolate (Linux) Best wishes. Mario ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] testing release candidate for 4.0.0
On Wed, Mar 25, 2009 at 04:31:24PM +0100, felix winkelmann wrote: I tested it on several systems (mingw(+msys), linux), but would appreciate if others could give it a try. Note that some minor recent trunk changes didn't make it, due to unclear portability. On OpenBSD 4.5 x86: Compiles both from the distributed C files, and also from C files generated (by Chicken 4) from the Scheme code. I get the following when running make fullcheck -- == gmake -f ./Makefile.bsd dist gmake[2]: Entering directory `/home/taylor/Source/Lisp/chicken-4.0.0' csi -s ./scripts/makedist.scm --platform=bsd CHICKEN=chicken Error: (open-input-file) cannot open file - No such file or directory: ./scripts/makedist.scm gmake[2]: *** [dist] Error 70 gmake[2]: Leaving directory `/home/taylor/Source/Lisp/chicken-4.0.0' gmake[1]: *** [compiler-check] Error 2 gmake[1]: Leaving directory `/home/taylor/Source/Lisp/chicken-4.0.0' gmake: *** [fullcheck] Error 2 == When issuing make check it runs to completion and appears to be successful (I notice no failures; but I'd be happy to supply a transcript if requested). -- Taylor Christopher Venable http://real.metasyntax.net:2357/ ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
