Re: [Chicken-hackers] bootstrapping (again)

[Felix]

From: Sven Hartrumpf <address@hidden>
Subject: [Chicken-hackers] bootstrapping (again)
Date: Tue, 13 Dec 2011 08:54:13 +0100 (CET)

> Hi all.
> 
> Is this a correct bootstrap script for building a git version
> from release 4.7.0.3-st (called chicken470)?
> 
> export PLATFORM=linux
> export ARCH=x86
> make C_COMPILER=gcc32 C_COMPILER_OPTIMIZATION_OPTIONS='-O2 
> -fomit-frame-pointer -march=core2' LINKER=gcc32 LINKER_OPTIONS= 
> PREFIX=/usr/local/chicken-master NOPTABLES=1 confclean spotless
> make C_COMPILER=gcc32 C_COMPILER_OPTIMIZATION_OPTIONS='-O2 
> -fomit-frame-pointer -march=core2' LINKER=gcc32 LINKER_OPTIONS= 
> PREFIX=/usr/local/chicken-master NOPTABLES=1 boot-chicken CHICKEN=chicken470
> make C_COMPILER=gcc32 C_COMPILER_OPTIMIZATION_OPTIONS='-O2 
> -fomit-frame-pointer -march=core2' LINKER=gcc32 LINKER_OPTIONS= 
> PREFIX=/usr/local/chicken-master NOPTABLES=1 CHICKEN=./chicken-boot

Those look right.

> make C_COMPILER=gcc32 C_COMPILER_OPTIMIZATION_OPTIONS='-O2 
> -fomit-frame-pointer -march=core2' LINKER=gcc32 LINKER_OPTIONS= 
> PREFIX=/usr/local/chicken-master NOPTABLES=1

This will compile with whatever chicken is in the path, or it might
(depending on your path) use the currently built one, which can be
problematic depending on the linker-path and other factors. After you
built with "CHICKEN=./chicken-boot" it is not necessary to build it
once again.

Is LD_LIBRARY_PATH globally set? When you get the errors, can you repeat
the exact command, prefixed with "LD_DEBUG=libs "? This will show which
libchicken is used - I assume there is a conflict here. But of course
it might be something completely different.


cheers,
felix