summaryrefslogtreecommitdiff
path: root/samples/moxie-unknown-elf/reported.by
diff options
context:
space:
mode:
authorAlexey Neyman <stilor@att.net>2018-11-24 06:14:07 (GMT)
committerAlexey Neyman <stilor@att.net>2018-12-01 18:10:51 (GMT)
commit40d5bf64408a0e103f8149f941ea50fbbb11dc91 (patch)
tree67532a4e3a2498ab5663bb400649ec847ced6ba7 /samples/moxie-unknown-elf/reported.by
parent172308cb1be5b23c816c19d0b9c84ba4910cbe80 (diff)
Add moxiebox as a choice for libc
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>
Diffstat (limited to 'samples/moxie-unknown-elf/reported.by')
-rw-r--r--samples/moxie-unknown-elf/reported.by9
1 files changed, 8 insertions, 1 deletions
diff --git a/samples/moxie-unknown-elf/reported.by b/samples/moxie-unknown-elf/reported.by
index 13d42a9..907a11f 100644
--- a/samples/moxie-unknown-elf/reported.by
+++ b/samples/moxie-unknown-elf/reported.by
@@ -1,3 +1,10 @@
reporter_name="Alexey Neyman"
reporter_url=""
-reporter_comment="Bare metal configuration for moxie architecture."
+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."