mirror of
https://github.com/crosstool-ng/crosstool-ng.git
synced 2025-01-02 02:56:40 +00:00
40d5bf6440
This required some rework of the libc selection, as moxiebox is a layer on top of another libc - newlib. Also, moxiebox'es host VM (`sandbox`) needs a libcrypto on the host. We will not have it if we're cross-compiling a canadian cross. Fortunately, all moxiebox needs from libcrypto is SHA256, and it already includes a standalone implementation of SHA256 in its runtime. Provide a little wrapper that allows moxiebox use that implementation for the host binary, too. Also, automate collecting/printing the list of all packages in a given category (e.g. LIBC or COMP_TOOLS), generate a list of all Kconfig symbols for a given category. Signed-off-by: Alexey Neyman <stilor@att.net>
11 lines
430 B
Plaintext
11 lines
430 B
Plaintext
reporter_name="Alexey Neyman"
|
|
reporter_url=""
|
|
reporter_comment="Bare metal configuration for moxie architecture.
|
|
|
|
It appears to generate a broken toolchain. E.g. newlib's CRT expects
|
|
symbols __bss_start__ and __bss_end__, while linker script generates
|
|
__bss_start (no underscores at the end) and no __bss_end__whatsoever.
|
|
|
|
This is not a bug in crosstool-NG. If you're interested in saving the
|
|
moxie, please report this upstream."
|