aboutsummaryrefslogtreecommitdiff
path: root/samples/moxie-unknown-moxiebox
Commit message (Collapse)AuthorAgeFilesLines
* moxiebox: Use newlib 4.2crosstool-ng-1.26.0Chris Packham2023-09-241-0/+1
| | | | | | | | | | | | | | moxie-unknown-moxiebox has problems building with newlib 4.3 ld: /lib/libc.a(libc_a-closer.o): in function `_close_r': newlib/libc/reent/closer.c:47: undefined reference to `_close' There are some Makefile changes in newlib 4.3 and it's likely previously this config was picking up `_close` from libsim.a. For now just pin the newlib version back to 4.2 in the moxie-unknown-moxiebox config. Resolves #2036 Signed-off-by: Chris Packham <judge.packham@gmail.com>
* Rename moxiebox to match its tupleAlexey Neyman2022-02-112-0/+10
| | | | Signed-off-by: Alexey Neyman <stilor@att.net>
* Allow short "moxiebox" aliasAlexey Neyman2018-12-102-10/+0
| | | | | | | | | | ... while making use of the new tunables. Also, unmark the moxie-elf as broken: the ld scripts installed by newlib can be found by the compiler and can link the binaries. Why the default script is broken is not ct-ng's problem... Signed-off-by: Alexey Neyman <stilor@att.net>
* Moxiebox requires target to be LEAlexey Neyman2018-12-071-0/+1
| | | | Signed-off-by: Alexey Neyman <stilor@att.net>
* Add moxiebox as a choice for libcAlexey Neyman2018-12-012-0/+9
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>