| 2016-12-05 15:15:20 |
Daniel Kochmański |
description |
It may be also broken for other linking implementations (mkcl, clasp). In ECL static library can't be build from other static libraries (because `ar' can work properly only on object files) and as far as I can see it has never planned to do that.
This effectively breaks also FASL bundles under certain conditions (monolithic-compile-bundle-op?).
For steps to reproduce see:
https://gitlab.com/embeddable-common-lisp/ecl/issues/274
https://gitlab.com/embeddable-common-lisp/ecl/issues/177
Since next release instead of allowing such combination[1] into C::BUILDER (which leads to broken binary) ECL will signal an error.
Proper solution is to use object files which were used to build static library used as input right now. Recently I've added documentation[2] for proper transition of input files into their build output.
[1] Static library being input file for :static-library target.
[2] https://common-lisp.net/project/ecl/static/ecldoc/Extensions.html#System-building |
It may be also broken for other linking implementations (mkcl, clasp). In ECL static library can't be build from other static libraries (because `ar' can work properly only on object files) and as far as I can see ECL has never planned to do that.
This effectively breaks also FASL bundles under certain conditions (monolithic-compile-bundle-op?).
For steps to reproduce see:
https://gitlab.com/embeddable-common-lisp/ecl/issues/274
https://gitlab.com/embeddable-common-lisp/ecl/issues/177
Since next release instead of allowing such combination[1] into C::BUILDER (which leads to broken binary) ECL will signal an error.
Proper solution is to use object files which were used to build static library used as input right now. Recently I've added documentation[2] for proper transition of input files into their build output.
[1] Static library being input file for :static-library target.
[2] https://common-lisp.net/project/ecl/static/ecldoc/Extensions.html#System-building |
|
