Hi greadley,
You might try exporting CSC_OPTIONS or CHICKEN_OPTIONS, which should be
inherited by the compiler when it's invoked by `chicken-install'.
I'm a bit surprised that setting C_INCLUDE_PATH didn't work. You might
try adding "-verbose" to CSC_OPTIONS as well, to see what flags are
being
That did the trick, I now have a working user installation of both
4.13.0 and 5.0.0. Thanks a lot for your help, Alexander.
chicken-belt is up and running, too. Yay!
On 2/24/19 4:45 PM, Alexander Shendi (Web.DE) wrote:
Hi Heinz,
AFAIK, this should work. Try extracting the tarball again and
Hi Heinz,
On 2019-02-24 13:30, ipc...@arcor.de wrote:
> Also, I'm a bit unsure how to proceed afterwards. My plan was as follows:
The steps you've laid out there should work. The fact that `make' is
trying to recompile from Scheme sources indicates that the timestamps on
the files extracted from
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 ...
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
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
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
