Re: [Chicken-hackers] Build problems

[Brandon J. Van Every]

Tony Sidaway wrote:
> The chicken-2.5 tarball, which I guess is a product of an automake
> build, builds executables that do find the libraries in /usr/local/lib
> (is this a libtool thing?)
>
> I guess this could be either a problem with Chicken's CMake
> configuration or else a limitation of CMake.  On the other hand
> perhaps it's just some cruftiness in my system.  I'll try building on
> another system and see what happens.

All paths to things that Chicken needs are supposed to be hardwired in 
*.h files.  They are determined at configuration time.  Chicken 
shouldn't be looking in /usr/local/lib unless you decided to install to 
/usr/local.  If that's what you decided, then that's where it looks.  
CMake doesn't search around in extra directories for stuff; I would 
consider that a bug, not a feature.

How old was that old copy of Chicken?  Maybe it didn't have the unified 
hardwired *.h files for paths, and used some other mechanism for finding 
stuff.  I can't promise that current builds are bug free, but we'd need 
to verify a library collision problem with current builds only, to 
consider it a problem worthy of fixing.  I just think the older builds 
were too ad-hoc to do much in the way of support or corner case checking.


Cheers,
Brandon Van Every