Re: [ANN] CHICKEN 5.2.0 release candidate available

[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: [Chicken-users] [ANN] CHICKEN 5.1.0 release candidate available

[Alexander Shendi (Web.DE)]

Operating system: NetBSD 8.99.42
Hardware platform: arm64 aka aarch64 
C Compiler: GCC 7.4.0 (nb3 2019 03 19) 
Installation works?: yes 
Tests work?: yes (exit status 0)
Installation of eggs works?: (r7rs egg) yes

Best Regards,

Alexander 

Am 8. Juni 2019 15:07:34 MESZ schrieb Peter Bex :
>Hello everyone,
>
>We are happy to announce the first release candidate of the upcoming
>CHICKEN 5.1.0.
>
>CHICKEN 5.1.0rc1 is now available at this location:
>https://code.call-cc.org/dev-snapshots/2019/06/08/chicken-5.1.0rc1.tar.gz
>
>The SHA256 sum of that tarball is
>d520bf83e446b67508768de90768724b8a2ebb1953e6ece873ce790162a1b671
>
>The most important change is a breaking one: Keywords are now
>completely
>distinct from symbols.  Keywords are no longer accepted as identifiers
>nor as type names, which may mean you'll need to pipe-quote them or
>disable keyword syntax on your projects.
>
>The other important new features are the new cond-expand, c-object and
>object forms in .egg files.
>
>The complete list of changes since version 5.0.0 is available here:
>https://code.call-cc.org/dev-snapshots/2019/06/08/NEWS
>
>(Note that I accidentally left the entry for 5.0.1 under 5.1.0.  5.1.0
>includes those changes as well, this will be fixed in the next RC or in
>the final release)
>
>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.1.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___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

Re: [Chicken-users] build failure and some questions about using chicken-belt

[Alexander Shendi (Web.DE)]

Hi Heinz,

AFAIK, this should work. Try extracting the tarball again and making with the 
correct environment variable.

Best Regards,

Alexander 

Am 24. Februar 2019 15:20:22 MEZ schrieb ipc...@arcor.de:
>Hi Alexander,
>
>Well spotted, I was indeed missing the #\S. However, after
>
>make ... confclean && make ... clean
>
>running make again still fails with the same error as before.
>
>Best wishes,
>-Heinz
>
>
>
>On 2/24/19 2:48 PM, Alexander Shendi (Web.DE) wrote:
>> Dear Heinz,
>> 
>> It maybe just a typo, but I noticed, you said you set a $CHICKENS env
>var, but in your make command you reference a $CHICKEN env var (without
>#\S).
>> 
>> To answer your other questions: I usually use the approach you
>propose, but I simply build each variant of CHICKEN in its own
>subdirectory with the appropriate PREFIX and PLATFORM make arguments.
>> 
>> I usually select each variant by invoking, e.g. $PREFIX/bin/csc or by
>adding $PREFIX/bin to $PATH.
>> 
>> Best Regards,
>> 
>> Alexander
>> 
>> Am 24. Februar 2019 13:30:39 MEZ schrieb ipc...@arcor.de:
>>> Hello,
>>>
>>> I would like to transition from my current system-wide installation
>of
>>> Chicken 4.13.0 to a coop of different Chickens installed in
>~/chickens,
>>>
>>> managed by chicken-belt. Namely, I want to have 4.13.0, 5.0.0, and a
>>> cross-chicken for MinGW (most likely based on 5.0.0) available.
>>>
>>> Steps taken so far:
>>>
>>> - create ~/chickens and set CHICKENS env var
>>> - Download & extracted the 4.13.0 and 5.0.0. tarballs
>>>
>>> Now trying to build 4.13.0 with
>>>
>>> $ make PLATFORM=linux PREFIX=$CHICKEN/4.13.0
>>>
>>> which fails with
>>>
>>> cat: buildid: No such file or directory
>>> cat: buildtag.h: No such file or directory
>>> chicken  build-version.scm -optimize-level 2 -include-path .
>>> -include-path ./ -inline -ignore-repository -feature
>chicken-bootstrap
>>> -no-warnings -specialize -types ./types.db   -explicit-use -no-trace
>>> -output-file build-version.c
>>> clang -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H
>>> -DC_ENABLE_PTABLES -c -Os -fomit-frame-pointer 
>-DC_BUILDING_LIBCHICKEN
>>>
>>> build-version.c -o build-version-static.o -I. -I./
>>> build-version.c:13:10: fatal error: 'buildtag.h' file not found
>>> #include "buildtag.h"
>>>   ^~~~
>>> 1 error generated.
>>> make: *** [rules.make:131: build-version-static.o] Error 1
>>>
>>> The build for 5.0.0 fails with the same error. How can I resolve
>this?
>>>
>>> Also, I'm a bit unsure how to proceed afterwards. My plan was as
>>> follows:
>>>
>>> - build 4.13.0
>>> - uninstall the system-wide install
>>> - add $CHICKENS/4.13.0 to PATH
>>> - chicken-install chicken-belt
>>> - chicken-select 4.13.0
>>> - remove $CHICKENS/4.13.0 from path, add $CHICKENS/use-this/bin
>>> - build 5.0.0.
>>>
>>> Would that work? Anything else I need to consider?
>>>
>>>
>>> Best wishes,
>>> -Heinz
>>>
>>>
>>> ___
>>> Chicken-users mailing list
>>> Chicken-users@nongnu.org
>>> https://lists.nongnu.org/mailman/listinfo/chicken-users
>> 
>> 
>> ___
>> Chicken-users mailing list
>> Chicken-users@nongnu.org
>> https://lists.nongnu.org/mailman/listinfo/chicken-users
>> 
>
>___
>Chicken-users mailing list
>Chicken-users@nongnu.org
>https://lists.nongnu.org/mailman/listinfo/chicken-users

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

Re: [Chicken-users] build failure and some questions about using chicken-belt

[Alexander Shendi (Web.DE)]

Dear Heinz,

It maybe just a typo, but I noticed, you said you set a $CHICKENS env var, but 
in your make command you reference a $CHICKEN env var (without #\S).

To answer your other questions: I usually use the approach you propose, but I 
simply build each variant of CHICKEN in its own subdirectory with the 
appropriate PREFIX and PLATFORM make arguments.

I usually select each variant by invoking, e.g. $PREFIX/bin/csc or by adding 
$PREFIX/bin to $PATH.

Best Regards,

Alexander 

Am 24. Februar 2019 13:30:39 MEZ schrieb ipc...@arcor.de:
>Hello,
>
>I would like to transition from my current system-wide installation of 
>Chicken 4.13.0 to a coop of different Chickens installed in ~/chickens,
>
>managed by chicken-belt. Namely, I want to have 4.13.0, 5.0.0, and a 
>cross-chicken for MinGW (most likely based on 5.0.0) available.
>
>Steps taken so far:
>
>- create ~/chickens and set CHICKENS env var
>- Download & extracted the 4.13.0 and 5.0.0. tarballs
>
>Now trying to build 4.13.0 with
>
>$ make PLATFORM=linux PREFIX=$CHICKEN/4.13.0
>
>which fails with
>
>cat: buildid: No such file or directory
>cat: buildtag.h: No such file or directory
>chicken  build-version.scm -optimize-level 2 -include-path . 
>-include-path ./ -inline -ignore-repository -feature chicken-bootstrap 
>-no-warnings -specialize -types ./types.db   -explicit-use -no-trace 
>-output-file build-version.c
>clang -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H 
>-DC_ENABLE_PTABLES -c -Os -fomit-frame-pointer  -DC_BUILDING_LIBCHICKEN
>
>build-version.c -o build-version-static.o -I. -I./
>build-version.c:13:10: fatal error: 'buildtag.h' file not found
>#include "buildtag.h"
>  ^~~~
>1 error generated.
>make: *** [rules.make:131: build-version-static.o] Error 1
>
>The build for 5.0.0 fails with the same error. How can I resolve this?
>
>Also, I'm a bit unsure how to proceed afterwards. My plan was as
>follows:
>
>- build 4.13.0
>- uninstall the system-wide install
>- add $CHICKENS/4.13.0 to PATH
>- chicken-install chicken-belt
>- chicken-select 4.13.0
>- remove $CHICKENS/4.13.0 from path, add $CHICKENS/use-this/bin
>- build 5.0.0.
>
>Would that work? Anything else I need to consider?
>
>
>Best wishes,
>-Heinz
>
>
>___
>Chicken-users mailing list
>Chicken-users@nongnu.org
>https://lists.nongnu.org/mailman/listinfo/chicken-users

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

Re: [Chicken-users] 5.0.0rc3 under Android/Termux

[Alexander Shendi (Web.DE)]

With this setup you should also be able to run the test suite. Thank you for 
sharing.

Best Regards,

Alexander 

Am 18. Oktober 2018 02:38:19 MESZ schrieb daniel szmulewicz 
:
>Hi everybody,
>
>Following Alexander's post on installing 5.0.0rc3 under Android/Termux,
>I
>would like to share some additional observations in the hope that some
>might find them useful.
>
>You can get shorten the installation steps if you build Chicken in a
>chrooted Termux. In the chroot environment, all the standard
>directories
>are in the standard places and writable, rendering the LD_LIBRARY_PATH
>configuration superfluous.
>
>$  make PLATFORM=android C_COMPILER=clang PREFIX=/usr
>$ make PLATFORM=android C_COMPILER=clang PREFIX=/usr install
>
>And you should be done.
>
>In summary, prior to installing Chicken Scheme in Termux, install
>PRoot,
>`pkg install proot', run termux-chroot to get a chrooted environment,
>then
>proceed with the build.
>
>A note of caution: this will install the files under the root
>directory, so
>you can't have multiple versions side by side. For this reason, I
>actually
>did something slightly different than the procedure described above.
>I've
>kept the prefix to my home directory, like Alexander, so I have Chicken
>5.0.0rc3 installed in $HOME/chickens/5.0.0rc3, and Chicken 4.13.0 in
>$HOME/chickens/4.13.0. I then created a symbolic link called current
>that
>points to the version I want to use. For example,
>$HOME/chickens/current
>points to $HOME/chickens/5.0.0rc3.
>
>Finally, I've created symbolic links in /usr/bin, /usr/lib,
>/usr/include
>and /usr/share referring to the current Chicken distribution (the files
>under $HOME/chickens/current). This is a one-time, manual process. When
>I
>want to switch between Chicken versions, I just change where `current'
>points to.
>
>In the end, this may have been overdoing it, and I am not at all sure
>that
>I would recommend this setup over fiddling with .bashrc to achieve the
>same
>results.
>
>By the way, `chicken-doc' is not available with 5.0.0rc3, so I've
>reverted
>to 4.13.0 because Geiser complains without it.
>
>Thanks!
>
>Daniel

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

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

[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 



Am 9. September 2018 14:30:12 MESZ schrieb 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=5.0.0rc1=5.0=status=id=summary=owner=type=priority=component=version=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= PREFIX= install check
>  $ /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

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

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

[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 

Am 11. August 2018 11:43:58 MESZ schrieb 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= PREFIX= install check
>  $ /bin/chicken-install spiffy
>
>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.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

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

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

Re: [Chicken-users] Chicken on Termux

[Alexander Shendi (web.de)]

Hi Phil, 

you have to set LD_LIBRARY_PATH explicitly :

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HOME/chicken-4.12.0/lib

Then you should be able to invoke "csi" directly. You don't need my patch, if 
you don't mind a linker warning message each time you run "csi". 

Best Regards, 

Alexander 

Am 13. Mai 2017 03:15:30 MESZ schrieb Phil Bewig <pbe...@gmail.com>:
>I began as John suggested with the following command line:
>
>TMPDIR=$HOME/tmp make C_COMPILER=clang PREFIX=$HOME/chicken-4.12.0
>PLATFORM=linux install
>
>This ran fine (about ten minutes) until it encountered an error on the
>line:
>
>clang -L. chicken.o batch-driver.o compiler.o optimizer.o lfa2.o
>compiler-syntax.o scrutinizer.o support.o c-platform.o c-backend.o -o
>chicken -lchicken -W1,-R"." -lm -ldl
>
>The error message is:
>
>./libchicken.so: undefined reference to '__android_log_vprint'
>clan-4.0: error: linker command failed with exit code 1 (use -v to see
>invocation)
>make: *** [rules.make:247: chicken] Error 1
>
>So I erased everything, untarred again, and did as Alexander suggested:
>
>TMPDIR=$HOME/tmp make C_COMPILER=clang PREFIX=$HOME/chicken-4.12.0
>PLATFORM=android install
>
>The compile completed successfully, but when I run ./csi I get an
>error:
>
>CANNOT LINK EXECUTABLE: could not load library "libchicken.so" needed
>by
>"./csi"; caused by library "libchicken.so" not found
>
>Of course, libchicken.so is in the same directory as csi. I suppose
>that is
>the linker error Alexander talked about. I have questions:
>
>1) How do I work around the link error and run csi?
>
>2) Alexander: How do I apply your patch? (I'm not adept with C.) Is
>your
>patch forward-compatible so it will work on future versions of chicken?
>
>3) Is there a way to compile chicken so the library is included
>statically
>and doesn't require a dynamically-loaded library? (I would prefer that
>to a
>patch.)
>
>Thanks again,
>
>Phil
>
>On Fri, May 12, 2017 at 6:16 PM, Alexander Shendi (web.de) <
>alexander.she...@web.de> wrote:
>
>> Dear Phil,
>>
>> It's me again.
>>
>> Some remarks:
>> I did successfully compile CHICKEN 4.12.0 on Termux/Android. Please
>use
>> that exact release as it contains several fixes for the Android
>platform.
>>
>> 1) I used PLATFORM=android as Termux uses Android's libc (Bionic)
>rather
>> than GNU libc.
>> 2) The complete make invocation I used was:
>>
>> TMPDIR=$HOME/tmp make C_COMPILER=clang PREFIX=$HOME/chickens/4.12.0
>> PLATFORM=android install
>>
>> 3) the Android dynamic linker is rather dumb and doesn't support the
>> --rpath feature used by the Makefile.
>> It spits out a warning to that effect every time you run csi/csc or
>an
>> executable made with csc.
>> This also screws up the CHICKEN test suite. I have a patch that works
>> around that
>> (see
>https://paste.call-cc.org/paste?id=a738f447edf76ecbaa7b47eeced51f
>> a138972add#a0)
>> But if you can live with the warning message and don't need to run
>the
>> test suite you don't need to apply the patch.
>>
>> 3) I did (see above).
>>
>> 4.1) CHICKEN 's library directory (e.g. $HOME/chickens/4.12.0/lib)
>must be
>> in your $LD_LIBRARY_PATH.
>> 4.2) If you want to install eggs (CHICKEN's version of packages) you
>must
>> say:
>> TMPDIR=$HOME/tmp chicken-install 
>>
>>
>> 5.) Good luck!
>>
>> 6.) Do not hesitate to ask for further info.
>>
>> Best Regards,
>>
>> Alexander
>>
>>
>> Am 12. Mai 2017 23:00:10 MESZ schrieb Phil Bewig <pbe...@gmail.com>:
>>>
>>> I recently purchased a Lenovo TAB2 A10 tablet computer and installed
>>> Termux, a unix-like environment, from the Play Store. I want to
>compile
>>> Chicken for my computer so I can have a Scheme REPL with me wherever
>I go.
>>> I have several questions:
>>>
>>> 1) What is the correct PLATFORM for the make command? Is it android?
>>> Termux isn't really android, it is its own version of unix, similar
>to
>>> Debian.
>>>
>>> 2) Are any of the optional features required or recommended for
>Termux?
>>>
>>> 3) Have any other Chicken users successfully compiled Chicken on
>Termux?
>>>
>>> 4) Is there anything else I need to know to compile Chicken on
>Termux?
>>>
>>> Thanks for your help.
>>>
>>> Phil
>>>
>>
>> --
>> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail
>> gesendet.
>>

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

Re: [Chicken-users] Chicken on Termux

[Alexander Shendi (web.de)]

Dear Phil, 

It's me again. 

Some remarks:
I did successfully compile CHICKEN 4.12.0 on Termux/Android. Please use that 
exact release as it contains several fixes for the Android platform. 

1) I used PLATFORM=android as Termux uses Android's libc (Bionic) rather than 
GNU libc. 
2) The complete make invocation I used was:

TMPDIR=$HOME/tmp make C_COMPILER=clang PREFIX=$HOME/chickens/4.12.0 
PLATFORM=android install

3) the Android dynamic linker is rather dumb and doesn't support the --rpath 
feature used by the Makefile. 
It spits out a warning to that effect every time you run csi/csc or an 
executable made with csc. 
This also screws up the CHICKEN test suite. I have a patch that works around 
that 
(see 
https://paste.call-cc.org/paste?id=a738f447edf76ecbaa7b47eeced51fa138972add#a0) 
But if you can live with the warning message and don't need to run the test 
suite you don't need to apply the patch. 

3) I did (see above). 

4.1) CHICKEN 's library directory (e.g. $HOME/chickens/4.12.0/lib) must  be in 
your $LD_LIBRARY_PATH. 
4.2) If you want to install eggs (CHICKEN's version of packages) you must say:
TMPDIR=$HOME/tmp chicken-install 


5.) Good luck! 

6.) Do not hesitate to ask for further info. 

Best Regards, 

Alexander 


Am 12. Mai 2017 23:00:10 MESZ schrieb Phil Bewig :
>I recently purchased a Lenovo TAB2 A10 tablet computer and installed
>Termux, a unix-like environment, from the Play Store. I want to compile
>Chicken for my computer so I can have a Scheme REPL with me wherever I
>go.
>I have several questions:
>
>1) What is the correct PLATFORM for the make command? Is it android?
>Termux
>isn't really android, it is its own version of unix, similar to Debian.
>
>2) Are any of the optional features required or recommended for Termux?
>
>3) Have any other Chicken users successfully compiled Chicken on
>Termux?
>
>4) Is there anything else I need to know to compile Chicken on Termux?
>
>Thanks for your help.
>
>Phil

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users