Re: csirc when transitioning from chicken 4 to 5

2020-01-15 Thread Matt Welland
Perfect! I was not aware of cond-expand. Thanks!

On Wed, Jan 15, 2020 at 11:28 AM Peter Bex  wrote:

> On Wed, Jan 15, 2020 at 11:00:02AM -0700, Matt Welland wrote:
> > I have not been able to figure out how to make a .csirc that works for
> both
> > chicken 4 and 5.
> >
> > (import (chicken platform)) is not legal for chicken 4 but
> > (chicken-version) is not available in chicken 5 until you've done the
> > import. Chicken and egg :)
>
> Try cond-expand;
>
> (cond-expand
>   (chicken-5
> (import (chicken platform)))
>   (chicken-4
> (use extras)))
>
> Cheers,
> Peter
>


-- 
--
Complexity is your enemy. Any fool can make something complicated.
It is hard to keep things simple. - Richard Branson.


Re: csirc when transitioning from chicken 4 to 5

2020-01-15 Thread Peter Bex
On Wed, Jan 15, 2020 at 11:00:02AM -0700, Matt Welland wrote:
> I have not been able to figure out how to make a .csirc that works for both
> chicken 4 and 5.
> 
> (import (chicken platform)) is not legal for chicken 4 but
> (chicken-version) is not available in chicken 5 until you've done the
> import. Chicken and egg :)

Try cond-expand;

(cond-expand
  (chicken-5
(import (chicken platform)))
  (chicken-4
(use extras)))

Cheers,
Peter


signature.asc
Description: PGP signature


csirc when transitioning from chicken 4 to 5

2020-01-15 Thread Matt Welland
I have not been able to figure out how to make a .csirc that works for both
chicken 4 and 5.

(import (chicken platform)) is not legal for chicken 4 but
(chicken-version) is not available in chicken 5 until you've done the
import. Chicken and egg :)

How about having chicken 5 csi load ".csirc5"?

Thanks
--
Complexity is your enemy. Any fool can make something complicated.
It is hard to keep things simple. - Richard Branson.


Re: [ANN] CHICKEN 5.2.0 release candidate available

2020-01-15 Thread Alexander Shendi (Web.DE)
Dear List,

OS: Debian 9.11, Linux 4.4.19, aarch64 Kernel, armv7hf user land. 
Hardware: Pinebook Pro (aarch64/arm64) 
Compiler: GCC 6.3.0-18+deb9u1

I have followed the instructions and done:

1. make PREFIX=$HOME/.local/chicken/5.2.0rc1 PLATFORM=linux C_COMPILER=gcc
2. make PREFIX=$HOME/.local/chicken/5.2.0rc1 PLATFORM=linux C_COMPILER=gcc 
install
3. make PREFIX=$HOME/.local/chicken/5.2.0rc1 PLATFORM=linux C_COMPILER=gcc check
4. ~/.local/chicken/5.2.0rc1/bin/chicken-install r7rs
5. ~/.local/chicken/5.2.0rc1/bin/chicken-install hyde

All steps succeeded (The output from step 3 was a bit confusing, but make 
proceeded without error). I chose to install the r7rs and Hyde eggs because I 
need them for my work.

Also, as you can see, the install is local to my home directory. 

Best Regards,

Alexander 

Am 12. Januar 2020 13:29:06 MEZ schrieb Peter Bex :
>Hello everyone,
>
>We are happy to announce the first release candidate of the upcoming
>CHICKEN 5.2.0.
>
>CHICKEN 5.2.0rc1 is now available at this location:
>https://code.call-cc.org/dev-snapshots/2020/01/12/chicken-5.2.0rc1.tar.gz
>
>The SHA256 sum of that tarball is
>bf651739d7b1588b9f8b860975171987cb81566627f6fbcdf956637d35089bdc
>
>This is mostly a maintenance and bugfix release.
>
>One important change might cause breakage of existing code: CHICKEN
>will
>now error out when you use -c with multiple files (see #1655) for more
>info.
>
>Another change that might expose bugs in existing code, thereby
>possibly breaking it is that modules won't pollute the global namespace
>anymore when imported.  This may expose missing imports in macro code,
>because an import won't make the imports available for compile-time
>code.
>See #1548 for more info.
>
>The complete list of changes since version 5.1.0 is available here:
>https://code.call-cc.org/dev-snapshots/2020/01/12/NEWS
>
>Please give it a test and report your findings to the mailing list.
>
>Here's a suggested test procedure:
>
>  $ make PLATFORM= PREFIX= install check
>  $ /bin/chicken-install pastiche
>
>If you want to build CHICKEN with a compiler other than the default
>one,
>just use C_COMPILER= (e.g., C_COMPILER=clang) on the make
>invocation.
>
>Of course, feel free to explore other supported build options (see the
>README file for more information) and actually use CHICKEN 5.2.0rc1 for
>your software.
>
>If you can, please let us know the following information about the
>environment you tested the RC tarball on:
>
>Operating system: (e.g., FreeBSD 12.0, Debian 9, Windows 10 mingw-msys
>under 
>mingw32)
>Hardware platform: (e.g., x86, x86-64, PPC)
>C Compiler: (e.g., GCC 6.4.0, clang 5.0.0)
>Installation works?: yes or no
>Tests work?: yes or no
>Installation of eggs works?: yes or no
>
>Thanks in advance!
>
>The CHICKEN Team

--
You have zero privacy anyway. Get over it.

Scott McNealy 1999

Re: srfi-19 for C5?

2020-01-15 Thread Kon Lovett
posix-utils should be available soon

> On Jan 15, 2020, at 7:20 AM, Sven Hartrumpf  wrote:
> 
> Hi all.
> 
> I found http://wiki.call-cc.org/eggref/5/srfi-19
> and assumed that SRFI-19 is supported by C5.
> But chicken-install fails because a dependency leads to posix-utils
> (and probably more eggs that are missing in C5).
> Is this analysis correct or is my cache broken?
> 
> Ciao
> Sven
> 




srfi-19 for C5?

2020-01-15 Thread Sven Hartrumpf
Hi all.

I found http://wiki.call-cc.org/eggref/5/srfi-19
and assumed that SRFI-19 is supported by C5.
But chicken-install fails because a dependency leads to posix-utils
(and probably more eggs that are missing in C5).
Is this analysis correct or is my cache broken?

Ciao
Sven