Summary
When cross-compiling, the active features do not represent target system
Metadata
- Id: c337dc81793fbafab07cdbd3070c17db8c57c495
- Trac id: 97
- Type: defect
- Reporter: felix
- Owner: felix
- Cc:
- Status: closed
- Component: core tools
- Estimated difficulty:
- Resolution: fixed
- Priority: not urgent at all
- Milestone:
- Version: 4.2.x
- Changetime: 2010-06-09 23:50:44 UTC
- Created: 2009-11-02 10:31:18 UTC
- Keywords: cross-development
Description
During the cross-compile, the feature-IDs for target architecture and operating system are not correct. We need to un-register those features and register features suitable for the target.
This will probably require a `-no-feature` option and build-variables for target architecture and platform.
The implications for this are extremely subtle, and this may be difficult to get right.
Changes and comments
[2009-12-01 15:27:56 UTC] felix changed description
[2009-12-01 15:27:56 UTC] felix removed milestone 4.3.0
[2010-05-07 12:04:19 UTC] felix changed priority from minor to not urgent at all
[2010-05-07 12:04:19 UTC] felix set keywords to cross-development
[2010-05-07 12:04:19 UTC] felix wrote:
One possible approach would be a `-no-feature ID` option to disable built-in features and a `make(3)` variable `CROSS_FEATURES` that holds `-[[no-]|]feature` options to be passed to `csc` when cross-compiling.
[2010-06-09 23:50:44 UTC] felix changed status from new to closed
[2010-06-09 23:50:44 UTC] felix set resolution to fixed
[2010-06-09 23:50:44 UTC] felix wrote:
In commit f2b3bf92fb606d42f1898b8ff914cb1c352d3c32, a make-variable named `TARGET_FEATURES` has been given, which should contain target-specific options that will be passed to `chicken` by `csc`. This, together with the `-no-feature` option added in 95ed1c2d2c1ae12558d80bf7f5b5e12441729dd2 should be a start.