Opened 8 years ago

Last modified 4 weeks ago

#125 assigned defect

cross-chicken should prefer loading uncompiled import libraries

Reported by: felix Owned by:
Priority: minor Milestone: 5.1
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 (8)

comment:1 Changed 8 years ago by felix

  • Milestone 4.3.0 deleted
  • Priority changed from major to minor

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

comment:3 in reply to: ↑ 2 Changed 8 years ago by felix

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 7 years ago by felix

  • Owner set to felix
  • Status changed from new to assigned

comment:5 Changed 7 years ago by felix

  • Owner felix deleted

comment:6 Changed 7 years ago by felix

  • Owner set to felix

comment:7 Changed 6 years ago by felix

  • Owner felix deleted

comment:8 Changed 4 weeks ago by sjamaan

  • Estimated difficulty set to medium
  • Milestone set to 5.1

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

Note: See TracTickets for help on using tickets.