On 9/6/06, Alejandro Forero Cuervo <[EMAIL PROTECTED]> wrote:
Maybe modules should try to continue working with older Chicken
versions?
We are already tring to do so, but this can sometimes be hard.
And maybe whenever a bad compiler bug (such as, IMHO, the
one for call/values) is found, a re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 5, 2006, at 10:13 PM, Shawn Rutledge wrote:
On 9/4/06, Brandon J. Van Every <[EMAIL PROTECTED]> wrote:
So, who has the real need to do cross-compilation?
Ideally tcc would even be fast enough for Chicken to compile on the
fly to native
On 9/4/06, Brandon J. Van Every <[EMAIL PROTECTED]> wrote:
So, who has the real need to do cross-compilation?
I'm using Chicken on the Zaurus (ARM processor). The approach I'm
using now is to actually compile Chicken on the Zaurus. (I do this on
a chroot image on a CF card, because OpenZaurus
On Tuesday 05 September 2006 01:08, Brandon J. Van Every wrote:
> Matthew Welland wrote:
> >
> > Why is it important for your build system to be exercised everywhere?
>
> It isn't important for CMake to be exercised everywhere. It's important
> for CMake to be exercised *extensively*. Right no
Hi all!
I've a strange problem when including macros from the
interpreter. For example, the file test.scm below runs
fine if csi first evals (use syntax-case) and then
includes it; but if csi directly includes the file
(which itself requires syntax-case), an error occurs:
test.scm -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry about that. While the 'hashes' code does protect against
`uint*_t' not begin available the 'mathh' did not. Fixed.
Best Wishes,
Kon
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)
iEYEARECAAYFAkT+GmcACgkQJJNoeGe+5O6NGgCfQrHP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 5, 2006, at 3:23 PM, Alejandro Forero Cuervo wrote:
It seems the sha1 egg is no longer installable in Chicken 2.3:
# /opt/chicken-2.3/bin/chicken-setup sha1
The extension sha1 does not exist.
Do you want to download it ? (yes/
Alejandro Forero Cuervo wrote:
Maybe modules should try to continue working with older Chicken
versions? And maybe whenever a bad compiler bug (such as, IMHO, the
one for call/values) is found, a release should be made right away
(even if it only the minor version number is increased, ala 2.41.
On 9/5/06, Alejandro Forero Cuervo <[EMAIL PROTECTED]> wrote:
(snip)
makes it impossible to use svnwiki; I don't know of a versions of
Chicken in which it works.
Now we are using Svnwiki in a production environment :)
http://wiki.freaks-unidos.net/weblogs/arhuaco/new%20job%20-%20svnwiki
IMHO,
It seems the sha1 egg is no longer installable in Chicken 2.3:
# /opt/chicken-2.3/bin/chicken-setup sha1
The extension sha1 does not exist.
Do you want to download it ? (yes/no/abort) [yes]
downloading catalog ...
downloading catalog from www.call-with-current-continuation.o
For CMake, if we solve the outstanding problems with Linux dependencies,
Windows eggs, and don't identify any new lurking problems, I believe we
should bill the CMake build as "beta quality." Why? Well, because I
just threw down the gauntlet to a SBCL booster about how much their
Windows buil
John Cowan wrote:
So CMake is very much the winner, probably because ./configure is doing
unnecessary tests.
Yes, Autoconf is very bloated in this regard. Those extra tests aren't
specified by us in configure.in, they're just what Autoconf does.
Also, autoconf is doing them twice. Once
I ran from-scratch CMake and autotools builds of the current Darcs head
on my Cygwin system with basic wall-clock timing (the "time" command
in bash). Take this with a grain of salt, YMMV, etc. etc.
cmake "cmake /opt/chicken/darcs": 1m23s
cmake "make": 9m10s
cmake "make install": 0m15s
cmake tota
I agree that Chicken has great potential on embedded Linux and
embedded Linux has a rosey future what with Motorola phones, Nokia
770, Sony Mylo, Pepperpad and ALP (new Palm OS) to name a few.
I have been developing an SDL based graphical console type app using
Chicken and testing it on my Sharp Z
On 9/5/06, Brandon J. Van Every <[EMAIL PROTECTED]> wrote:
And now they're done, in Darcs.
Excellent.
Two perceived reasons for building only from .c files:
- someone may need to cross-compile
- someone may be unable to get a bootstrapped chicken to compile .scm to .c
I have serious reser
On 9/5/06, Brandon J. Van Every <[EMAIL PROTECTED]> wrote:
Linux appears to have a bug in CMake, not the build itself. I will
wager that a workaround is pretty trivial, just shoving more
dependencies in somewhere. But the bug, whatever it is, does need to be
reported.
I've done so.
Who ca
Matthew Welland wrote:
Why is it important for your build system to be exercised everywhere?
It isn't important for CMake to be exercised everywhere. It's
important for CMake to be exercised *extensively*. Right now, without
a nightly build, that means being exercised by lotsa Chicken
felix winkelmann wrote:
Ow - harsh words. Ok... let me think... What I need:
- fully workable build (cmake/autotools) on Linux and OS X, both from
repo and tarball
(doesn't work yet) - I can try to assist here
Linux appears to have a bug in CMake, not the build itself. I will
wager that a
18 matches
Mail list logo
