[Chicken-users] [ANN] CHICKEN 5.0.0 release candidate 1 available

[Peter Bex]

Hello everyone,

After many years of development, we are happy to announce the first
release candidate of the upcoming CHICKEN 5.0.0. This represents the
largest change in CHICKEN since the 4.0.0 release.

Most importantly, we have completely overhauled the module layout so
that it should make more sense where each identifier is located.
For a quick overview of where things are, see the page we used for
discussion of these changes:
https://wiki.call-cc.org/core-libraries-reorganization

The manual has of course also been updated to reflect these new modules:
https://wiki.call-cc.org/man/5/Included%20modules

Other notable features are:
- Full numeric tower
- A new declarative egg description format for chicken-install
- Improved support for static linking (eggs are now also compiled statically)
- "Deployment" mode has been dropped as it was less portable and reliable
than static linking.
- Builds are fully bit-for-bit reproducible (for core, but user code too)
- Random numbers now use a better PRNG than libc rand() (namely, WELL512)
- Core has gone on a diet: several libraries have been moved to eggs, like
srfi-1, srfi-13, srfi-14, srfi-18, srfi-69, and several other things.

The (very long!) complete list of changes since version 4.13.0 is
available here: https://code.call-cc.org/dev-snapshots/2018/08/11/NEWS

CHICKEN 5.0.0rc1 is now available at this location:
https://code.call-cc.org/dev-snapshots/2018/08/11/chicken-5.0.0rc1.tar.gz

The SHA256 sum of that tarball is
fb8af147e7965761dd212b53162b181d4c9473906fd889e719c71624bca65957

Please give it a test and report your findings to the mailing list.

Here's a suggested test procedure:

$ make PLATFORM=<platform> PREFIX=<some dir> install check
$ <some dir>/bin/chicken-install spiffy

If you want to build CHICKEN with a compiler other than the default one,
just use C_COMPILER=<the 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.0.0rc1 for
your software. The tireless CHICKEN team has been busy porting eggs to
CHICKEN 5 already, so you will find that many eggs you've been using have
already been ported. Check out the ever-growing list at
https://wiki.call-cc.org/chicken-projects/egg-index-5.html

If you want to port your code to CHICKEN 5, you'll note the number of
changes are so large that it can be overwhelming. That's why we've
written up a porting guide to help you get your code over to the new
version: https://wiki.call-cc.org/porting-c4-to-c5
Please feel free to add to the guide if you run into problems that aren't
yet addressed on this wiki page.

If you can, please let us know the following information about the
environment you tested the RC tarball on:

Operating system: (e.g., FreeBSD 11.1, 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

[Alexander Shendi (web.de)]

Operating System: Debian 9.4 under Chrome OS.
Hardware: ARM64 aka aarch64
C Compiler: gcc 6.3
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes

Many thanks to the CHICKEN team for making this happen.

Best Regards,

Alexander

Post by Peter Bex
Hello everyone,
After many years of development, we are happy to announce the first
release candidate of the upcoming CHICKEN 5.0.0. This represents the
largest change in CHICKEN since the 4.0.0 release.
Most importantly, we have completely overhauled the module layout so
that it should make more sense where each identifier is located.
For a quick overview of where things are, see the page we used for
https://wiki.call-cc.org/core-libraries-reorganization
The manual has of course also been updated to reflect these new
https://wiki.call-cc.org/man/5/Included%20modules
- Full numeric tower
- A new declarative egg description format for chicken-install
- Improved support for static linking (eggs are now also compiled statically)
- "Deployment" mode has been dropped as it was less portable and reliable
than static linking.
- Builds are fully bit-for-bit reproducible (for core, but user code too)
- Random numbers now use a better PRNG than libc rand() (namely, WELL512)
- Core has gone on a diet: several libraries have been moved to eggs, like
srfi-1, srfi-13, srfi-14, srfi-18, srfi-69, and several other things.
The (very long!) complete list of changes since version 4.13.0 is
available here: https://code.call-cc.org/dev-snapshots/2018/08/11/NEWS
https://code.call-cc.org/dev-snapshots/2018/08/11/chicken-5.0.0rc1.tar.gz
The SHA256 sum of that tarball is
fb8af147e7965761dd212b53162b181d4c9473906fd889e719c71624bca65957
Please give it a test and report your findings to the mailing list.
$ make PLATFORM=<platform> PREFIX=<some dir> install check
$ <some dir>/bin/chicken-install spiffy
If you want to build CHICKEN with a compiler other than the default one,
just use C_COMPILER=<the 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.0.0rc1 for
your software. The tireless CHICKEN team has been busy porting eggs to
CHICKEN 5 already, so you will find that many eggs you've been using have
already been ported. Check out the ever-growing list at
https://wiki.call-cc.org/chicken-projects/egg-index-5.html
If you want to port your code to CHICKEN 5, you'll note the number of
changes are so large that it can be overwhelming. That's why we've
written up a porting guide to help you get your code over to the new
version: https://wiki.call-cc.org/porting-c4-to-c5
Please feel free to add to the guide if you run into problems that aren't
yet addressed on this wiki page.
If you can, please let us know the following information about the
Operating system: (e.g., FreeBSD 11.1, 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

[Peter Sommerfeld]

A scheme/chicken newbie here (second attempt).

Post by Peter Bex
After many years of development, we are happy to announce the first
release candidate of the upcoming CHICKEN 5.0.0. This represents
the largest change in CHICKEN since the 4.0.0 release.

I have compiled it on Win10 with mingw-64 with cmd.exe

Post by Peter Bex
make PLATFORM=mingw PREFIX=C:/Users/peter/chicken ARCH=x86-64 install
check

I added ARCH because without it compiling failed on chicken 4.

Result:
23 tests completed in 0.172 seconds
23 (100.00%) tests passed
0 (0.00%) tests failed
-- utf-8 tests --

TOTALS:
2447 tests completed in 1.188 seconds
2447 (100.00%) tests passed
0 (0.00%) tests failed

A few stresstests seems to have failed. The transscript is too long to
post it here. Of course, can be done if required.

Thanks all for your effort!

Peter

PS: waiting for system and mailbox egg ...

[Peter Bex]

Post by Peter Sommerfeld
A scheme/chicken newbie here (second attempt).

Hi Peter,

Welcome (again) to CHICKEN!

Post by Peter Sommerfeld

Post by Peter Bex
After many years of development, we are happy to announce the first
release candidate of the upcoming CHICKEN 5.0.0. This represents
the largest change in CHICKEN since the 4.0.0 release.

I have compiled it on Win10 with mingw-64 with cmd.exe

Excellent!

Post by Peter Sommerfeld

Post by Peter Bex
make PLATFORM=mingw PREFIX=C:/Users/peter/chicken ARCH=x86-64 install
check

I added ARCH because without it compiling failed on chicken 4.

Should not be necessary as far as I know.

Post by Peter Sommerfeld
23 tests completed in 0.172 seconds
23 (100.00%) tests passed
0 (0.00%) tests failed
-- utf-8 tests --
2447 tests completed in 1.188 seconds
2447 (100.00%) tests passed
0 (0.00%) tests failed
A few stresstests seems to have failed. The transscript is too long to
post it here. Of course, can be done if required.

I don't understand, can you elaborate on what failed exactly?

Cheers,
Peter

[Thomas Chust]

Post by Peter Bex
[...]
After many years of development, we are happy to announce the first
release candidate of the upcoming CHICKEN 5.0.0. This represents the
largest change in CHICKEN since the 4.0.0 release.
[...]

Hello,

thanks for all the hard work, it's good to see CHICKEN 5.0 getting
close to completion :-)

Post by Peter Bex
[...]
If you can, please let us know the following information about the
[...]

Operating system: Linux Mint 18.3
Hardware platform: x86-64
C Compiler: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.10)
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes

Ciao,
Thomas

[Claude Marinier]

Good afternoon,

Operating system: Ubuntu 18.04.1 LTS
Hardware platform: x86_64 (AMD A8-7600)
C Compiler: gcc 7.3.0
Installation works?: yes
Tests work?: yes
Installation of eggs works?: fails to install 'format'

***@GuloGulo:~/Programming/scheme$ chicken-install format
Server error:
Error: [Server] no such extension or version
"format"
#f
Server error:
Error: [Server] no such extension or version
"format"
#f
Error: extension or version not found: "format"

I must be missing something. Could the previous installation of Chicken
4,.13.0 be interfering?


Building a simple time stamp program fails.
csc timestamp.scm
./timestamp > prologue.scm
Error: unbound variable: command-line-arguments
Call history:
timestamp.scm:70: command-line-arguments <--
That should be in process-context which is included. Add this and try again.
(declare (uses process-context))
Fails again.
sc timestamp.scm
timestamp.o: In function `f_154':
timestamp.c:(.text+0x612): undefined reference to
`C_process_2dcontext_toplevel'
collect2: error: ld returned 1 exit status


Removing the offending call and the declaration reveals another issue: it
cannot find seconds->local-time. So, I added this.
(declare (uses time))
Does not work.
timestamp.c:(.text+0x5f3): undefined reference to `C_time_toplevel'
Then I added this.
(declare (uses time posix))
Same error.

I have not worked with Chicken is several months. Am I missing something
obvious?

Thank you.

[Peter Bex]

Post by Claude Marinier
Error: [Server] no such extension or version
"format"
#f
Error: [Server] no such extension or version
"format"
#f
Error: extension or version not found: "format"
I must be missing something. Could the previous installation of Chicken
4,.13.0 be interfering?

Hi Claude,

The format egg has not yet been ported to CHICKEN 5, so that's why
it cannot be installed.

Post by Claude Marinier
Building a simple time stamp program fails.
csc timestamp.scm
./timestamp > prologue.scm
Error: unbound variable: command-line-arguments
timestamp.scm:70: command-line-arguments <--
That should be in process-context which is included. Add this and try again.
(declare (uses process-context))
Fails again.
sc timestamp.scm
timestamp.c:(.text+0x612): undefined reference to
`C_process_2dcontext_toplevel'
collect2: error: ld returned 1 exit status
Removing the offending call and the declaration reveals another issue: it
cannot find seconds->local-time. So, I added this.
(declare (uses time))
Does not work.

There is no "time" unit. In general, you should not be dealing with
units. In CHICKEN 4 that's sometimes required when building statically,
but in CHICKEN 5 that should always never be necessary.

Post by Claude Marinier
timestamp.c:(.text+0x5f3): undefined reference to `C_time_toplevel'
Then I added this.
(declare (uses time posix))
Same error.

You'd need to (import (chicken time posix)), I think. That should
take care of all the dependencies for you.

Cheers,
Peter

[Claude Marinier]

...

Post by Peter Bex
The format egg has not yet been ported to CHICKEN 5, so that's why
it cannot be installed.

Hi Peter,
That explains a lot. I see my favourite egg is also not ported: linenoise.
I will wait.

Post by Peter Bex

Post by Claude Marinier
Building a simple time stamp program fails.
csc timestamp.scm
./timestamp > prologue.scm
Error: unbound variable: command-line-arguments
timestamp.scm:70: command-line-arguments <--

There is no "time" unit. In general, you should not be dealing with
units. In CHICKEN 4 that's sometimes required when building statically,
but in CHICKEN 5 that should always never be necessary.

Post by Claude Marinier
timestamp.c:(.text+0x5f3): undefined reference to `C_time_toplevel'
Then I added this.
(declare (uses time posix))
Same error.

You'd need to (import (chicken time posix)), I think. That should
take care of all the dependencies for you.

Works well. Thanks.

Installed the following eggs without issue: srfi-1, srfi-13, srfi-14,
srfi-69.

Chicken 5 is a lot closer.

Thank you.

[Christian Kellermann]

Post by Peter Bex
...

Post by Peter Bex
The format egg has not yet been ported to CHICKEN 5, so that's why
it cannot be installed.

Hi Peter,
That explains a lot. I see my favourite egg is also not ported: linenoise.
I will wait.

I have just ported linenoise to chicken 5. It should be available
via chicken-install soonish. Can you give it a try?

Thanks,

Christian

[Leonardo Taccari]

Hello Peter and the entire CHICKEN community!
just some reports on trying the first RC on some NetBSD machines
(TLDR; everything seems running fine!).

Post by Peter Bex
[...]
If you can, please let us know the following information about the
[...]

Operating system: NetBSD
Hardware platform: aarch64, amd64
C Compiler: gcc 6.4.0
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes

Both running NetBSD-current (8.99.15 on the amd64 machine and
8.99.23 on the aarch64 (a Pinebook)).

NetBSD/aarch64 is a pretty new port (for NetBSD) but I can confirm
that also there all tests passes and the `spiffy' egg correctly
install!


Thank you very much and keep up the good work!

[Peter Bex]

Hi all,

I tested on Haiku.

Operating system: Haiku "Walter" revision hrev50904
Hardware platform: x86
C Compiler: GCC 5.4.0
Installation works?: yes
Tests work?: no
Installation of eggs works?: no

I ran into some trouble with a few eggs, which I've fixed since.

I've also posted two patches for CHICKEN core to chicken-hackers.
These add a workaround for Haiku's broken stat(), which caused the
core tests to fail, and a fix for chicken-install's (platform ...)
clause, which caused some trouble getting the memory-mapped-files
egg to install correctly.

Cheers,
Peter

[Peter Bex]

Hi all,

I also took some time to test on an old Hurd VM I had lying around.

Operating system: Debian GNU/Hurd 0.9 (Mach 1.8+git20171101)
Hardware platform: x86
C Compiler: GCC 7.2.1
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes

Cheers,
Peter

[Kristian Lein-Mathisen]

Hi all,
and sorry about the late response on this one.

On my main Arch Linux, everything I tested has worked except building
statically against `check-errors` (ticket 1506
<https://bugs.call-cc.org/ticket/1506>).

Operating system: Arch Linux
Hardware platform: x86-64
C Compiler: GCC 8.2.0
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes

I also tested this on a win10 with make PLATFORM=mingw-msys install check:

Operating system: Win10
Hardware platform: x86-64
C Compiler: GCC 8.2.0 (rev1 msys2)
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes

Note that I had to install the "diff" tool to make the check succeed.
Here's a summary of the problems I encoutered with C5rc1 on Windows 10:

- when linking statically, csc is looking for ".o" files (Kooda is looking
into this I think) , improper patch here
<http://paste.call-cc.org/paste?id=25502dfa7ad26f2a11ed5b49319b3d99666217a1>
- pathname wierdness, see this paste
<http://paste.call-cc.org/paste?id=ef119e96c6c1be75b8ef851abd6cf19cf949361a>
- generated <egg>.install.bat file produces copy syntax error (see this
paste
<http://paste.call-cc.org/paste?id=7414404ddc5d8137e5da60be663a749b29c8fbcc>
)

Apart from these minor glitches, the CHICKEN 5 experience has been
wonderful.

I wanted to try static linking with CHICKEN 5 and this is the result, a
poor man's TeamViewer:
https://gist.github.com/kristianlm/16bbe626b54ad9b4e00fb8617d026bec
K.

Post by Peter Bex
Hi all,
I also took some time to test on an old Hurd VM I had lying around.
Operating system: Debian GNU/Hurd 0.9 (Mach 1.8+git20171101)
Hardware platform: x86
C Compiler: GCC 7.2.1
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes
Cheers,
Peter
_______________________________________________
Chicken-users mailing list
https://lists.nongnu.org/mailman/listinfo/chicken-users

[Peter Bex]

Hi Kris,

Many thanks for testing, especially on Windows (which can be pretty grueling!).

Post by Kristian Lein-Mathisen
- when linking statically, csc is looking for ".o" files (Kooda is looking
into this I think) , improper patch here
<http://paste.call-cc.org/paste?id=25502dfa7ad26f2a11ed5b49319b3d99666217a1>

I filed https://bugs.call-cc.org/ticket/1514 for this

Post by Kristian Lein-Mathisen
- pathname wierdness, see this paste
<http://paste.call-cc.org/paste?id=ef119e96c6c1be75b8ef851abd6cf19cf949361a>

I filed https://bugs.call-cc.org/ticket/1515 for this.

Post by Kristian Lein-Mathisen
- generated <egg>.install.bat file produces copy syntax error (see this
paste
<http://paste.call-cc.org/paste?id=7414404ddc5d8137e5da60be663a749b29c8fbcc>

I filed https://bugs.call-cc.org/ticket/1516 for this.

Post by Kristian Lein-Mathisen
Apart from these minor glitches, the CHICKEN 5 experience has been
wonderful.

Excellent!

Post by Kristian Lein-Mathisen
I wanted to try static linking with CHICKEN 5 and this is the result, a
https://gist.github.com/kristianlm/16bbe626b54ad9b4e00fb8617d026bec

This is really impressive, especially if you see how little code is
needed for it!

Cheers,
Peter

[k***@upyum.com]

Hi there! Here are some tests results. :D

Operating system: Devuan unstable, glibc 2.27
Hardware platform: x86-64
C Compiler: GCC 8.2.0
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes (spiffy)

Operating system: Alpine Linux edge, musl-libc 1.1.19
Hardware platform: arm
C Compiler: GCC 6.4.0
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes (spiffy)


Little cross compilation test:

- Building a toolchain, on the first system (Devuan x86-64), for the
second system (Alpine ARM): works

- Building a static hello world for ARM on x86-64: works

- Building spiffy (and its dependencies) with the cross toolchain: works

- Building a simple static web server binary for ARM on x86-64: works

- Running both static binaries on the target system: works!! \o/

Just got a hint of warning from glibc because it requires the dynamic
library at runtime on the target system for some functions, but it
worked anyways!

[Norman Gray]

Operating system: OS X 10.10.5 (Yosemite)
Hardware platform: x86-64
C Compiler: Apple LLVM version 7.0.2 (clang-700.1.81)
Installation works?: yes
Tests work?: yes
Installation of eggs works?: no

The tests produced a number of warnings and errors which I think were
either expected or harmless, but I don't think any tests failed (though
there wasn't a big 'nnn tests passed 0 tests failed' at the end).

The installation of spiffy failed with:

[...]
/Data/tools/chicken-5.0.0rc1-clang/bin/csc -host -D
compiling-extension -J -s -setup-mode -I
/Users/norman/.chicken-install/cache/memory-mapped-files -C
-I/Users/norman/.chicken-install/cache/memory-mapped-files -O2 -d1
/Users/norman/.chicken-install/cache/memory-mapped-files/memory-mapped-files.scm
-o
/Users/norman/.chicken-install/cache/memory-mapped-files/memory-mapped-files.so
/Users/norman/.chicken-install/cache/memory-mapped-files/memory-mapped-files.c:395:85:
error: use of undeclared identifier 'MAP_ANONYMOUS'
t11=C_set_block_item(lf[14] /* memory-mapped-files#map/anonymous
*/,0,C_fix((C_word)MAP_ANONYMOUS));
^
/Data/tools/chicken-5.0.0rc1-clang/include/chicken/chicken.h:1023:56:
note: expanded from macro 'C_fix'
#define C_fix(n) ((C_word)((C_uword)(n) <<
C_FIXNUM_SHIFT) | C_FIXNUM_BIT)
^
/Data/tools/chicken-5.0.0rc1-clang/include/chicken/chicken.h:995:59:
note: expanded from macro 'C_set_block_item'
#define C_set_block_item(x,i,y) (C_block_item(x, i) = (y))
^
1 error generated.

Error: shell command terminated with non-zero exit status 256: 'clang'
'/Users/norman/.chicken-install/cache/memory-mapped-files/memory-mapped-files.c'
-o
'/Users/norman/.chicken-install/cache/memory-mapped-files/memory-mapped-files.o'
-c -fno-strict-aliasing -fwrapv -fno-common -DHAVE_CHICKEN_CONFIG_H
-m64 -DC_ENABLE_PTABLES -Os -fomit-frame-pointer -fPIC -DPIC -DC_SHARED
-I/Users/norman/.chicken-install/cache/memory-mapped-files
-I/Data/tools/chicken-5.0.0rc1-clang/include/chicken

Error: shell command terminated with nonzero exit code
256
"sh
/Users/norman/.chicken-install/cache/memory-mapped-files/memory-mapped-files.build.sh"



I've got logs of both the build/test and the spiffy install, if it would
be useful to send them off-list.

If I have time, I'll also try the build on a more recent version of the
OS.

Best wishes,

Norman

[Norman Gray]

Post by Norman Gray
C Compiler: Apple LLVM version 7.0.2 (clang-700.1.81)

...and I should mention that I did the same test with the system 'gcc',
which is the GCC front-end with the LLVM back-end, and got the same
result.

I should further note that yes, these are quite old OS and compiler
versions, but this machine is still my main desktop, so it's by no means
obsolete.

Best wishes,

Norman

[Peter Bex]

[...]
/Data/tools/chicken-5.0.0rc1-clang/bin/csc -host -D compiling-extension
-J -s -setup-mode -I
/Users/norman/.chicken-install/cache/memory-mapped-files -C
-I/Users/norman/.chicken-install/cache/memory-mapped-files -O2 -d1 /Users/norman/.chicken-install/cache/memory-mapped-files/memory-mapped-files.scm
-o /Users/norman/.chicken-install/cache/memory-mapped-files/memory-mapped-files.so
error: use of undeclared identifier 'MAP_ANONYMOUS'
t11=C_set_block_item(lf[14] /* memory-mapped-files#map/anonymous
*/,0,C_fix((C_word)MAP_ANONYMOUS));

This is the memory-mapped-files egg, which is a dependency of spiffy.
The MAP_ANON definition is marked as deprecated on GNU systems in favour
of MAP_ANONYMOUS, but other systems still hang on to MAP_ANON, sometimes
offering an alias as MAP_ANONYMOUS. I've now changed it so that if
MAP_ANONYMOUS is undefined but MAP_ANON is defined, it is made an alias.

I've published a new release, which should appear on the egg servers shortly.

Cheers,
Peter

[Justin Meiners]

Operating system: Ubuntu 18.04
Hardware platform: x86-64
C Compiler: GCC 7.3
Installation works?: yes
Tests work?: yes
Installation of eggs works?: no. I just tried installing spiffy and some
srfi's. No matter what eggs I tried it couldn't find anything.

This is a repy to this post:
http://lists.nongnu.org/archive/html/chicken-users/2018-08/msg00004.html

(I am not sure how to reply to an old post as I was not on the mailing list
when it was sent.)

Thanks,
- Justin

[Peter Bex]

Post by Claude Marinier
Operating system: Ubuntu 18.04
Hardware platform: x86-64
C Compiler: GCC 7.3
Installation works?: yes
Tests work?: yes
Installation of eggs works?: no. I just tried installing spiffy and some
srfi's. No matter what eggs I tried it couldn't find anything.

Hi Justin,

That's a bit worrying; Ubuntu is a really standard platform and it should
work. Could you paste the output of a failing chicken-install command,
with the -verbose flag?

Cheers,
Peter

[Justin Meiners]

Here is the output with the verbose flag. I am installed in a non-standard
directory which is in my PATH.

$ chicken-install spiffy -verbose
spiffy not cached

Error: extension or version not found: "spiffy"

Post by Peter Bex

Post by Claude Marinier
Operating system: Ubuntu 18.04
Hardware platform: x86-64
C Compiler: GCC 7.3
Installation works?: yes
Tests work?: yes
Installation of eggs works?: no. I just tried installing spiffy and some
srfi's. No matter what eggs I tried it couldn't find anything.

Hi Justin,
That's a bit worrying; Ubuntu is a really standard platform and it should
work. Could you paste the output of a failing chicken-install command,
with the -verbose flag?
Cheers,
Peter

[Peter Bex]

Post by Justin Meiners
Here is the output with the verbose flag. I am installed in a non-standard
directory which is in my PATH.
$ chicken-install spiffy -verbose
spiffy not cached
Error: extension or version not found: "spiffy"

Can you try the following command as well?

chicken-install -update-db -verbose

Cheers,
Peter

[Justin PYrofex]

Sorry for the dealy. Since updating the RC3 this has been fixed.

Operating system: Ubuntu 18.04
Hardware platform: x86-64
C Compiler: GCC 7.3
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes

Thanks,
- Justin

Post by Justin Meiners

Post by Justin Meiners
Here is the output with the verbose flag. I am installed in a

non-standard

Post by Justin Meiners
directory which is in my PATH.
$ chicken-install spiffy -verbose
spiffy not cached
Error: extension or version not found: "spiffy"

Can you try the following command as well?
chicken-install -update-db -verbose
Cheers,
Peter