Opened 15 years ago
Last modified 13 months ago
#125 assigned defect
cross-chicken should prefer loading uncompiled import libraries
Reported by: | felix winkelmann | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 6.0.0 |
Component: | core tools | Version: | 4.2.x |
Keywords: | Cc: | ||
Estimated difficulty: | medium |
Description
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.
Change History (12)
comment:1 Changed 15 years ago by
Milestone: | 4.3.0 |
---|---|
Priority: | major → minor |
comment:2 follow-up: 3 Changed 15 years ago by
comment:3 Changed 15 years ago by
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 ofrequire-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.
comment:4 Changed 15 years ago by
Owner: | set to felix winkelmann |
---|---|
Status: | new → assigned |
comment:5 Changed 14 years ago by
Owner: | felix winkelmann deleted |
---|
comment:6 Changed 14 years ago by
Owner: | set to felix winkelmann |
---|
comment:7 Changed 13 years ago by
Owner: | felix winkelmann deleted |
---|
comment:8 Changed 7 years ago by
Estimated difficulty: | → medium |
---|---|
Milestone: | → 5.1 |
This has been sitting in the issues for far too long. Let's see if we can tackle this in 5.1.
comment:9 Changed 6 years ago by
Milestone: | 5.1 → 5.2 |
---|
comment:10 Changed 5 years ago by
Milestone: | 5.2 → 5.3 |
---|
comment:12 Changed 13 months ago by
Milestone: | 5.4 → 6.0.0 |
---|
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 ofrequire-extension
.