cross-chicken should prefer loading uncompiled import libraries

[felix winkelmann]

Unless in -host mode, chicken(1) should prefer loading import libraries from the current directory in source form (.scm), or it will possibly load import libs compiled for the target architecture.

[Mario Domenech Goulart]

Would it possibly be the reason why I get a message like "wrong ELF class: ELFCLASS32" when cross compiling from x86_64 to x86?

I could "fix" if by using include instead of require-extension.

[felix winkelmann]

Replying to mario:

Would it possibly be the reason why I get a message like "wrong ELF class: ELFCLASS32" when cross compiling from x86_64 to x86?

I could "fix" if by using include instead of require-extension.

Yes, this is possible. If you are currently in a chicken-install run that produces .so's and these .so's are located in the current-directory, and -setup-mode is given then any chicken tools that try to require-extension a module of this name. We need -setup-mode for those cases when this behaviour is actually intended (an egg build uses compiled modules that are products of the current build) - for these eggs cross-compilation has to be done manually.

[sjamaan]

This has been sitting in the issues for far too long. Let's see if we can tackle this in 5.1.

[sjamaan]

Aaand postponing again :)