Opened 12 years ago

Last modified 8 days ago

#125 assigned defect

cross-chicken should prefer loading uncompiled import libraries

Reported by: felix winkelmann Owned by:
Priority: minor Milestone: 5.4
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 (11)

comment:1 Changed 12 years ago by felix winkelmann

Milestone: 4.3.0
Priority: majorminor

comment:2 Changed 12 years ago by 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.

comment:3 in reply to:  2 Changed 12 years ago by 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.

comment:4 Changed 11 years ago by felix winkelmann

Owner: set to felix winkelmann
Status: newassigned

comment:5 Changed 11 years ago by felix winkelmann

Owner: felix winkelmann deleted

comment:6 Changed 11 years ago by felix winkelmann

Owner: set to felix winkelmann

comment:7 Changed 10 years ago by felix winkelmann

Owner: felix winkelmann deleted

comment:8 Changed 4 years ago by sjamaan

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 2 years ago by sjamaan

Milestone: 5.15.2

comment:10 Changed 22 months ago by felix winkelmann

Milestone: 5.25.3

comment:11 Changed 8 days ago by sjamaan

Milestone: 5.35.4

Aaand postponing again :)

Note: See TracTickets for help on using tickets.