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