CHICKEN Scheme

Summary

cross-chicken should prefer loading uncompiled import libraries

Metadata

Id: 5d7b441fb542d9c3d073123a0da9589eab7dc183
Trac id: 125
Type: defect
Reporter: felix
Owner:
Cc:
Status: new
Component: core tools
Estimated difficulty: medium
Resolution:
Priority: minor
Milestone: 6.0.0
Version: 4.2.x
Changetime: 2023-11-06 22:15:30 UTC
Created: 2009-11-21 12:38:13 UTC
Keywords:

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.

Changes and comments

[2009-12-01 15:28:16 UTC] felix changed priority from major to minor

[2009-12-01 15:28:16 UTC] felix removed milestone 4.3.0

[2009-12-02 12:35:35 UTC] mario wrote:

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.

[2009-12-02 14:09:04 UTC] felix wrote:

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.