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

[Peter Bex]

Hello all,

The second release candidate for CHICKEN 5.0.0 is now available for
download:

http://code.call-cc.org/dev-snapshots/2018/09/09/chicken-5.0.0rc2.tar.gz

The sha256sum of that tarball is:

237c88fcdd0d31f01923d9c5d0e4a564d22cdee98687a4e1daa2bc97d173e460

The list of changes since 4.13.0 is available here (which is the
same as that of 5.0.0rc1):

http://code.call-cc.org/dev-snapshots/2018/09/09/NEWS

Quite a few issues have been fixed, especially with chicken-install
and quoting (most of those on Windows). For an overview of fixed
tickets since 5.0.0rc1, see the Trac page:

http://bugs.call-cc.org/query?status=closed&version=5.0.0rc1&milestone=5.0&group=status&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority

Please give this new release candidate a try and report your findings
to the mailing list. Here's a suggested test procedure:

$ make PLATFORM=<platform> PREFIX=<directory> install check
$ <directory>/bin/chicken-install pastiche

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

Operating system: (e.g., FreeBSD 10.1, Debian 8, Windows 7 mingw-msys)
Hardware platform: (e.g., x86, x86-64, PPC)
C Compiler: (e.g., GCC 4.9.2, clang 3.6)
Installation works?: yes or no
Tests work?: yes or no
Installation of eggs works?: yes or no

Thanks in advance!

The CHICKEN Team

[Peter Bex]

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

Operating system: FreeBSD 11.2
Hardware platform: x86-64
C Compiler: GCC 6.4.0
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes

Cheers,
Peter

[Alexander Shendi (Web.DE)]

Operating System: OpenBSD 6.3 (with patches)
Hardware Platform: amd64/x86_64
C compiler: Clang 5.0.1 (system compiler)
Installation works? : yes
Tests work: yes
Installation of eggs works: r7rs works, pastiche fails.

Best Regards,

Alexander

Post by Peter Bex
Hello all,
The second release candidate for CHICKEN 5.0.0 is now available for
http://code.call-cc.org/dev-snapshots/2018/09/09/chicken-5.0.0rc2.tar.gz
237c88fcdd0d31f01923d9c5d0e4a564d22cdee98687a4e1daa2bc97d173e460
The list of changes since 4.13.0 is available here (which is the
http://code.call-cc.org/dev-snapshots/2018/09/09/NEWS
Quite a few issues have been fixed, especially with chicken-install
and quoting (most of those on Windows). For an overview of fixed
http://bugs.call-cc.org/query?status=closed&version=5.0.0rc1&milestone=5.0&group=status&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority
Please give this new release candidate a try and report your findings
$ make PLATFORM=<platform> PREFIX=<directory> install check
$ <directory>/bin/chicken-install pastiche
If you can, please let us know the following information about the
Operating system: (e.g., FreeBSD 10.1, Debian 8, Windows 7 mingw-msys)
Hardware platform: (e.g., x86, x86-64, PPC)
C Compiler: (e.g., GCC 4.9.2, clang 3.6)
Installation works?: yes or no
Tests work?: yes or no
Installation of eggs works?: yes or no
Thanks in advance!
The CHICKEN Team

[Thomas Chust]

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

Operating system: Linux Mint 18.3 (based on Ubuntu 16.04)
Hardware platform: x86-64
C Compiler: GCC 8.2.0
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes

Ciao,
Thomas

[J K]

Operating system: Arch Linux
Hardware platform: x86-64
C Compiler: GCC 8.2.1
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes (matchable and fmt)

Cheers,
Julius

Post by Peter Bex
Hello all,
The second release candidate for CHICKEN 5.0.0 is now available for
http://code.call-cc.org/dev-snapshots/2018/09/09/chicken-5.0.0rc2.tar.gz
237c88fcdd0d31f01923d9c5d0e4a564d22cdee98687a4e1daa2bc97d173e460
The list of changes since 4.13.0 is available here (which is the
http://code.call-cc.org/dev-snapshots/2018/09/09/NEWS
Quite a few issues have been fixed, especially with chicken-install
and quoting (most of those on Windows). For an overview of fixed
http://bugs.call-cc.org/query?status=closed&version=5.0.0rc1&milestone=5.0&group=status&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority
Please give this new release candidate a try and report your findings
$ make PLATFORM=<platform> PREFIX=<directory> install check
$ <directory>/bin/chicken-install pastiche
If you can, please let us know the following information about the
Operating system: (e.g., FreeBSD 10.1, Debian 8, Windows 7 mingw-msys)
Hardware platform: (e.g., x86, x86-64, PPC)
C Compiler: (e.g., GCC 4.9.2, clang 3.6)
Installation works?: yes or no
Tests work?: yes or no
Installation of eggs works?: yes or no
Thanks in advance!
The CHICKEN Team
_______________________________________________
Chicken-users mailing list
https://lists.nongnu.org/mailman/listinfo/chicken-users

[Jörg F. Wittenberger]

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

Operating system: MINGW64_NT-10.0
Hardware platform: x86-64
C Compiler: gcc.exe (Rev1, Built by MSYS2 project) 8.2.0
Installation works?: yes
Tests work?: yes
Installation of eggs works?: no

Installation of eggs fails like this (for all eggs; immediately):

$ chicken-install.exe pastiche

Error: extension or version not found: "pastiche"

Cheers,

/Jörg

[Jörg F. Wittenberger]

Hi all,

who is running chicken on Windows 10 here? How do you manage? I'm not sold
to msys; I just tried first time and failed miserably.

Any idea how to do a better setup (for chicken 5 release candidates)
welcome.


Maybe we can fix the support for msys2 nevertheless;
So far I found two issues on Windows 10 + msys2 + mingw-w64:

1. chicken-install does not pick up the contents of setup.defaults by
itself.

Workaround: chicken-install -defaults
/usr/local/share/chicken/setup.defaults

-- which is saying: give the defaults from the installation on the
command line again.
-- This does the download and generates the build scripts (*.build.bat)

2. Using "start" to open a window running cmd.exe I found that I can not
call chicken-do using the full path. As it is in the PATH variable I tried
to copy the invocation line with only the path leading to chicken-do
removed.

This leads to:
/usr/local/bin/csc -host -D compiling-extension -J -s -setup-mode -I
C:\msys64\home\... ... ....so
creating subprocess failed

Best

/Jörg

Post by Jörg F. Wittenberger

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

Operating system: MINGW64_NT-10.0
Hardware platform: x86-64
C Compiler: gcc.exe (Rev1, Built by MSYS2 project) 8.2.0
Installation works?: yes
Tests work?: yes
Installation of eggs works?: no
$ chicken-install.exe pastiche
Error: extension or version not found: "pastiche"

[Kristian Lein-Mathisen]

Hi Joerg,

I was trying C5rc1 on win10 i few weeks ago and had to do some tweaking to
get it working og msys2 (which was surprisingly comfortable to use).

I also had a problem with chicken-install not downloading anything at
first. The symptom became clearer when I did chicken-install -update-db. I
realised I wasn't using an absolute path for PREFIX when invoking make. Doing
something like make PLATFORM=mingw-msys PREFIX=C:/c5/ solved the issue,
maybe you've run into the same problem?

I never tried to change the defaults, so this may be completely unrelated.
K.

On Wed, Sep 12, 2018, 16:15 Jörg F. Wittenberger <

Post by Jörg F. Wittenberger
Hi all,
who is running chicken on Windows 10 here? How do you manage? I'm not sold
to msys; I just tried first time and failed miserably.
Any idea how to do a better setup (for chicken 5 release candidates)
welcome.
Maybe we can fix the support for msys2 nevertheless;
1. chicken-install does not pick up the contents of setup.defaults by
itself.
Workaround: chicken-install -defaults
/usr/local/share/chicken/setup.defaults
-- which is saying: give the defaults from the installation on the
command line again.
-- This does the download and generates the build scripts (*.build.bat)
2. Using "start" to open a window running cmd.exe I found that I can not
call chicken-do using the full path. As it is in the PATH variable I tried
to copy the invocation line with only the path leading to chicken-do
removed.
/usr/local/bin/csc -host -D compiling-extension -J -s -setup-mode -I
C:\msys64\home\... ... ....so
creating subprocess failed
Best
/Jörg

Post by Jörg F. Wittenberger

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

Operating system: MINGW64_NT-10.0
Hardware platform: x86-64
C Compiler: gcc.exe (Rev1, Built by MSYS2 project) 8.2.0
Installation works?: yes
Tests work?: yes
Installation of eggs works?: no
$ chicken-install.exe pastiche
Error: extension or version not found: "pastiche"

_______________________________________________
Chicken-users mailing list
https://lists.nongnu.org/mailman/listinfo/chicken-users

[Jörg F. Wittenberger]

Hi Kristian,

I don't have the Windows machine close. I'm not perfectly sure, but I
should not have specify a PREFIX at all. My intention was first and
foremost to test that a default installation done by a windows novice using
hints from the wiki works.

Surprisingly this went well up to the compile.

The first issue I ran in could likely go away using your suggestion.

The second I'm afraid will not. The generated build scripts just do not
work on my system. As I'm a windows novice using msys2 first time, I'm
cautious to actually assign the blame. My guess is that the windows cmd.exe
should eventually execute the build scripts. If that's true than it does
not work because, wait for it, my cmd.exe does not accept the command when
it is given with path. It wants to do the lookup itself. At least that's
what it looks alike. I changed the "@echo off" to "@echo on" and it
perfectly works until there is this '/usr/local/bin/chicken-do' ... if I
replace this with just chicken-do it starts... just to break down when it
tries to execute csc the same way.

Anything I could do to track this down?

Best

/Jörg

Post by Kristian Lein-Mathisen
Hi Joerg,
I was trying C5rc1 on win10 i few weeks ago and had to do some tweaking to
get it working og msys2 (which was surprisingly comfortable to use).
I also had a problem with chicken-install not downloading anything at
first. The symptom became clearer when I did chicken-install -update-db.
I realised I wasn't using an absolute path for PREFIX when invoking make.
Doing something like make PLATFORM=mingw-msys PREFIX=C:/c5/ solved the
issue, maybe you've run into the same problem?
I never tried to change the defaults, so this may be completely unrelated.
K.
On Wed, Sep 12, 2018, 16:15 Jörg F. Wittenberger <

Post by Jörg F. Wittenberger
Hi all,
who is running chicken on Windows 10 here? How do you manage? I'm not
sold to msys; I just tried first time and failed miserably.
Any idea how to do a better setup (for chicken 5 release candidates)
welcome.
Maybe we can fix the support for msys2 nevertheless;
1. chicken-install does not pick up the contents of setup.defaults by
itself.
Workaround: chicken-install -defaults
/usr/local/share/chicken/setup.defaults
-- which is saying: give the defaults from the installation on the
command line again.
-- This does the download and generates the build scripts
(*.build.bat)
2. Using "start" to open a window running cmd.exe I found that I can
not call chicken-do using the full path. As it is in the PATH variable I
tried to copy the invocation line with only the path leading to
chicken-do removed.
/usr/local/bin/csc -host -D compiling-extension -J -s -setup-mode -I
C:\msys64\home\... ... ....so
creating subprocess failed
Best
/Jörg

Post by Jörg F. Wittenberger

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

Operating system: MINGW64_NT-10.0
Hardware platform: x86-64
C Compiler: gcc.exe (Rev1, Built by MSYS2 project) 8.2.0
Installation works?: yes
Tests work?: yes
Installation of eggs works?: no
$ chicken-install.exe pastiche
Error: extension or version not found: "pastiche"

_______________________________________________
Chicken-users mailing list
https://lists.nongnu.org/mailman/listinfo/chicken-users

[Kristian Lein-Mathisen]

Hi Jorg,

If I'm not mistaken, the Readme mentions says that you have to specify a
PREFIX for Windows builds. I'm guilty os trying the same "shortcut". And
obs: use forward slashes and include the drive letter and colon!

I don't know what's happing with the absolute-pathname trouble - I never
ran into that issue. Could the generated absolute pathnames be wrong due to
the same issue?

K.

On Sat, Sep 15, 2018, 15:26 Jörg F. Wittenberger <

Post by Jörg F. Wittenberger
Hi Kristian,
I don't have the Windows machine close. I'm not perfectly sure, but I
should not have specify a PREFIX at all. My intention was first and
foremost to test that a default installation done by a windows novice using
hints from the wiki works.
Surprisingly this went well up to the compile.
The first issue I ran in could likely go away using your suggestion.
The second I'm afraid will not. The generated build scripts just do not
work on my system. As I'm a windows novice using msys2 first time, I'm
cautious to actually assign the blame. My guess is that the windows cmd.exe
should eventually execute the build scripts. If that's true than it does
not work because, wait for it, my cmd.exe does not accept the command when
it is given with path. It wants to do the lookup itself. At least that's
perfectly works until there is this '/usr/local/bin/chicken-do' ... if I
replace this with just chicken-do it starts... just to break down when it
tries to execute csc the same way.
Anything I could do to track this down?
Best
/Jörg

Post by Kristian Lein-Mathisen
Hi Joerg,
I was trying C5rc1 on win10 i few weeks ago and had to do some tweaking to
get it working og msys2 (which was surprisingly comfortable to use).
I also had a problem with chicken-install not downloading anything at
first. The symptom became clearer when I did chicken-install -update-db.
I realised I wasn't using an absolute path for PREFIX when invoking

make.

Post by Kristian Lein-Mathisen
Doing something like make PLATFORM=mingw-msys PREFIX=C:/c5/ solved the
issue, maybe you've run into the same problem?
I never tried to change the defaults, so this may be completely unrelated.
K.
On Wed, Sep 12, 2018, 16:15 Jörg F. Wittenberger <

Post by Jörg F. Wittenberger
Hi all,
who is running chicken on Windows 10 here? How do you manage? I'm not
sold to msys; I just tried first time and failed miserably.
Any idea how to do a better setup (for chicken 5 release candidates)
welcome.
Maybe we can fix the support for msys2 nevertheless;
1. chicken-install does not pick up the contents of setup.defaults by
itself.
Workaround: chicken-install -defaults
/usr/local/share/chicken/setup.defaults
-- which is saying: give the defaults from the installation on the
command line again.
-- This does the download and generates the build scripts (*.build.bat)
2. Using "start" to open a window running cmd.exe I found that I can
not call chicken-do using the full path. As it is in the PATH variable

I

Post by Kristian Lein-Mathisen

Post by Jörg F. Wittenberger
tried to copy the invocation line with only the path leading to
chicken-do removed.
/usr/local/bin/csc -host -D compiling-extension -J -s -setup-mode -I
C:\msys64\home\... ... ....so
creating subprocess failed
Best
/Jörg

Post by Jörg F. Wittenberger

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

Operating system: MINGW64_NT-10.0
Hardware platform: x86-64
C Compiler: gcc.exe (Rev1, Built by MSYS2 project) 8.2.0
Installation works?: yes
Tests work?: yes
Installation of eggs works?: no
$ chicken-install.exe pastiche
Error: extension or version not found: "pastiche"

_______________________________________________
Chicken-users mailing list
https://lists.nongnu.org/mailman/listinfo/chicken-users

[Jörg F. Wittenberger]

Thanks Kristian,

problem solved:

Operating system: MINGW64_NT-10.0
Hardware platform: x86-64
C Compiler: gcc.exe (Rev1, Built by MSYS2 project) 8.2.0
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes


Surprisingly the pathname issue went away. I guess this is already
documented in the README "disguised" as "Cygwin will not be able to find
the chicken shared libraries until Windows is rebooted".

Thanks again for all the work which went into CHICKEN.

/Jörg

Post by Kristian Lein-Mathisen
Hi Jorg,
If I'm not mistaken, the Readme mentions says that you have to specify a
PREFIX for Windows builds. I'm guilty os trying the same "shortcut". And
obs: use forward slashes and include the drive letter and colon!
I don't know what's happing with the absolute-pathname trouble - I never
ran into that issue. Could the generated absolute pathnames be wrong due to
the same issue?
K.
On Sat, Sep 15, 2018, 15:26 Jörg F. Wittenberger <

Post by Jörg F. Wittenberger
Hi Kristian,
I don't have the Windows machine close. I'm not perfectly sure, but I
should not have specify a PREFIX at all. My intention was first and
foremost to test that a default installation done by a windows novice using
hints from the wiki works.
Surprisingly this went well up to the compile.
The first issue I ran in could likely go away using your suggestion.
The second I'm afraid will not. The generated build scripts just do not
work on my system. As I'm a windows novice using msys2 first time, I'm
cautious to actually assign the blame. My guess is that the windows
cmd.exe should eventually execute the build scripts. If that's true than
it does not work because, wait for it, my cmd.exe does not accept the
command when it is given with path. It wants to do the lookup itself. At
on" and it perfectly works until there is this
'/usr/local/bin/chicken-do' ... if I replace this with just chicken-do
it starts... just to break down when it tries to execute csc the same
way.
Anything I could do to track this down?
Best
/Jörg

Post by Kristian Lein-Mathisen
Hi Joerg,
I was trying C5rc1 on win10 i few weeks ago and had to do some
tweaking to get it working og msys2 (which was surprisingly
comfortable to use).
I also had a problem with chicken-install not downloading anything at
first. The symptom became clearer when I did chicken-install
-update-db. I realised I wasn't using an absolute path for PREFIX when
invoking

make.

Post by Kristian Lein-Mathisen
Doing something like make PLATFORM=mingw-msys PREFIX=C:/c5/ solved the
issue, maybe you've run into the same problem?
I never tried to change the defaults, so this may be completely
unrelated. K.
On Wed, Sep 12, 2018, 16:15 Jörg F. Wittenberger <

Post by Jörg F. Wittenberger
Hi all,
who is running chicken on Windows 10 here? How do you manage? I'm not
sold to msys; I just tried first time and failed miserably.
Any idea how to do a better setup (for chicken 5 release candidates)
welcome.
Maybe we can fix the support for msys2 nevertheless;
1. chicken-install does not pick up the contents of setup.defaults by
itself.
Workaround: chicken-install -defaults
/usr/local/share/chicken/setup.defaults
-- which is saying: give the defaults from the installation on the
command line again.
-- This does the download and generates the build scripts (*.build.bat)
2. Using "start" to open a window running cmd.exe I found that I can
not call chicken-do using the full path. As it is in the PATH variable

I

Post by Kristian Lein-Mathisen

Post by Jörg F. Wittenberger
tried to copy the invocation line with only the path leading to
chicken-do removed.
/usr/local/bin/csc -host -D compiling-extension -J -s -setup-mode
-I C:\msys64\home\... ... ....so
creating subprocess failed
Best
/Jörg

Post by Jörg F. Wittenberger

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

Operating system: MINGW64_NT-10.0
Hardware platform: x86-64
C Compiler: gcc.exe (Rev1, Built by MSYS2 project) 8.2.0
Installation works?: yes
Tests work?: yes
Installation of eggs works?: no
$ chicken-install.exe pastiche
Error: extension or version not found: "pastiche"

_______________________________________________
Chicken-users mailing list
https://lists.nongnu.org/mailman/listinfo/chicken-users

[Kristian Lein-Mathisen]

Hi,
Operating system: arch linux
Hardware platform: x86-64
C Compiler: GCC 8.20
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes (but not pastiche)

And on my phone:


Operating system: android 8.0.0
Hardware platform: arm
C Compiler: clang 6.0.1
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes (but not pastiche)


I'm og solar power right now and can't test on Win10.

K.

[Arthur Maciel]

Hi! Congratulations to the CHICKEN Team!

Operating system: Linux Mint 17
Hardware platform: x86-64
C Compiler: GCC 4.9.4
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes - awful (pastiche couldn't be found on
server)

Best,
Arthur


On Fri, Sep 14, 2018 at 4:32 PM Kristian Lein-Mathisen <

Post by Kristian Lein-Mathisen
Hi,

Operating system: arch linux
Hardware platform: x86-64
C Compiler: GCC 8.20
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes (but not pastiche)

Operating system: android 8.0.0
Hardware platform: arm
C Compiler: clang 6.0.1
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes (but not pastiche)
I'm og solar power right now and can't test on Win10.
K.
_______________________________________________
Chicken-users mailing list
https://lists.nongnu.org/mailman/listinfo/chicken-users

[Kristian Lein-Mathisen]

And a Win10 test:


Operating system: win 10 (msys2)
Hardware platform: x86-64
C Compiler: GCC
Installation works?: yes
Tests work?: -not tested-
Installation of eggs works?: yes (nrepl)


This is the make command that worked for me:

make PLATFORM=mingw-msys PREFIX=C:/c5/ ARCH=x86_64 install

I tried with PREFIX=C:/msys64/c5 first, which produced errors when running
`chicken-install -update-db`, but I don't have enough battery to
investagate this, sorry! It's reporting a funny path like
`C:/msys64/c5/share/\\modules.db`. But with `PREFIX=C:/c5`, it works.

K.

Post by Kristian Lein-Mathisen
Hi,

Operating system: arch linux
Hardware platform: x86-64
C Compiler: GCC 8.20
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes (but not pastiche)

Operating system: android 8.0.0
Hardware platform: arm
C Compiler: clang 6.0.1
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes (but not pastiche)
I'm og solar power right now and can't test on Win10.
K.

[querent]

_______________________________________________
Chicken-users mailing list
Chicken-***@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

[Peter Bex]

Better late than never?

Absolutely!

Operating system: android 7.0
Hardware platform: aarch64
C Compiler: gcc 7.3.0
Installation works?: no
Tests work?: N/A
Installation of eggs works?: N/A
I was following Alexander Shendl's instructions to build in termux
(chicken 4.12, but I thought it might work for 5.0.0 too, perhaps
$ TMPDIR=$HOME/tmp make C_COMPILER=clang PREFIX=$HOME/chickens/5.0.0
PLATFORM=android install
[all the echoing snipped]
clang -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H
-DC_ENABLE_PTABLES -c -Os -fomit-frame-pointer -DC_BUILDING_LIBCHICKEN
library.c -o library-static.o -I. -I./
chicken eval.scm -optimize-level 2 -include-path . -include-path ./
-inline -ignore-repository -feature chicken-bootstrap -no-warnings
-specialize -consult-types-file ./types.db -explicit-use -no-trace
-output-file eval.c \
-emit-import-library chicken.eval \
-emit-import-library chicken.load
make: chicken: Command not found
make: *** [rules.make:788: eval.c] Error 127
perhaps there's something I'm not doing right here?

Could you check the timestamp of eval.c is newer than all of the
following Scheme files?

- eval.scm
- chicken.blob.import.scm
- chicken.condition.import.scm
- chicken.foreign.import.scm
- chicken.internal.import.scm
- chicken.keyword.import.scm
- chicken.platform.import.scm

Please check them after untarring and after the failed build. Maybe
something is touching those files. Also, did you untar on the device,
or copy the files? If the latter, you'd have to copy with preservation
of time stamps.

Cheers,
Peter

[Kristian Lein-Mathisen]

Hi Querent,

Just in case it is helpful, I built c5 successfully on Termux like this:

make PLATFORM=android PREFIX=$HOME/c5/ install

Installing clang also gives an gcc executable/alias for me. I don't know
what the default TMPDIR is, but that too works here.

I untared directly on my device, so Peter's suggestion is probably in the
right direction.

K.

Post by Peter Bex

Better late than never?

Absolutely!

Operating system: android 7.0
Hardware platform: aarch64
C Compiler: gcc 7.3.0
Installation works?: no
Tests work?: N/A
Installation of eggs works?: N/A
I was following Alexander Shendl's instructions to build in termux
(chicken 4.12, but I thought it might work for 5.0.0 too, perhaps
$ TMPDIR=$HOME/tmp make C_COMPILER=clang PREFIX=$HOME/chickens/5.0.0
PLATFORM=android install
[all the echoing snipped]
clang -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H
-DC_ENABLE_PTABLES -c -Os -fomit-frame-pointer

-DC_BUILDING_LIBCHICKEN

library.c -o library-static.o -I. -I./
chicken eval.scm -optimize-level 2 -include-path . -include-path ./
-inline -ignore-repository -feature chicken-bootstrap -no-warnings
-specialize -consult-types-file ./types.db -explicit-use -no-trace
-output-file eval.c \
-emit-import-library chicken.eval \
-emit-import-library chicken.load
make: chicken: Command not found
make: *** [rules.make:788: eval.c] Error 127
perhaps there's something I'm not doing right here?

Could you check the timestamp of eval.c is newer than all of the
following Scheme files?
- eval.scm
- chicken.blob.import.scm
- chicken.condition.import.scm
- chicken.foreign.import.scm
- chicken.internal.import.scm
- chicken.keyword.import.scm
- chicken.platform.import.scm
Please check them after untarring and after the failed build. Maybe
something is touching those files. Also, did you untar on the device,
or copy the files? If the latter, you'd have to copy with preservation
of time stamps.
Cheers,
Peter
_______________________________________________
Chicken-users mailing list
https://lists.nongnu.org/mailman/listinfo/chicken-users

[querent]

_______________________________________________
Chicken-users mailing list
Chicken-***@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

[querent]

_______________________________________________
Chicken-users mailing list
Chicken-***@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

[Peter Bex]

Operating system: MacOS X 10.5.8
Hardware platform: PPC
C Compiler: gcc 4.0.1 (in Xcode 4.1.3)
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes (r7rs)
Though I had to change a few paths in Makefile.macosx to get this to work.
It seems that Xcode has changed its structure quite a bit since.
Is it worth documenting this anywhere?

Considering PowerPC OS X is unsupported and unmaintained (AFAIK)
I don't think that's necessary. People who are still running it
probably know how to deal with such issues (like you have).

If you think it's important enough, feel free to add a wiki page.

Cheers,
Peter