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
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.
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?
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
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
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
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
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
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
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:
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
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
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
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
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
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
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
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.
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
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
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
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
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
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
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
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
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
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
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
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
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
31 matches
Mail list logo
