89963644ab
arch/x86 set CROSSDEV only under Cygwin, so everywhere else the build used the bare tool names and got the host compiler. On Linux that is a native gcc which can produce i486 ELF objects, which is what the board README assumes. On macOS it is Apple clang, and on Apple Silicon that cannot target i386 in any form -- so there is no configuration in which the default works and a cross toolchain is not optional. Default it to i686-elf-, which Homebrew packages and which accepts the -march=i486 -mtune=i486 already in ARCHCPUFLAGS. arch/x86_64 has had exactly this stanza for its own toolchain all along; this is the same shape. The Cygwin assignment becomes ?= to match, so that a CROSSDEV passed in from the environment or the command line is honoured rather than overridden. Note for anyone tempted by the toolchain they already have: a 64-bit x86 compiler with -m32 is not a substitute unless it was built with multilib. Homebrew's x86_64-elf-gcc compiles 32-bit objects perfectly happily and has no 32-bit libgcc to link them against, so the entire build succeeds and only the final link fails, on __udivdi3, __divdi3, __moddi3 and __udivmoddi4. `x86_64-elf-gcc -print-multi-lib' prints just `.;', which is the toolchain saying so up front. Signed-off-by: Marco Casaroli <marco.casaroli@gmail.com> Assisted-by: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .github | ||
| arch | ||
| audio | ||
| binfmt | ||
| boards | ||
| cmake | ||
| crypto | ||
| Documentation | ||
| drivers | ||
| dummy | ||
| fs | ||
| graphics | ||
| include | ||
| libs | ||
| mm | ||
| net | ||
| openamp | ||
| pass1 | ||
| sched | ||
| syscall | ||
| tools | ||
| video | ||
| wireless | ||
| .asf.yaml | ||
| .codespell-ignore-lines | ||
| .codespellrc | ||
| .editorconfig | ||
| .gitignore | ||
| .gitmessage | ||
| .pre-commit-config.yaml | ||
| .yamllint | ||
| AUTHORS | ||
| CMakeLists.txt | ||
| CONTRIBUTING.md | ||
| INVIOLABLES.md | ||
| Kconfig | ||
| LICENSE | ||
| Makefile | ||
| NOTICE | ||
| README.md | ||
| ReleaseNotes | ||
Apache NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOSs (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).
For brevity, many parts of the documentation will refer to Apache NuttX as simply NuttX.
Getting Started
First time on NuttX? Read the Getting Started guide! If you don't have a board available, NuttX has its own simulator that you can run on terminal.
Documentation
You can find the current NuttX documentation on the Documentation Page.
Alternatively, you can build the documentation yourself by following the Documentation Build Instructions.
The old NuttX documentation is still available in the Apache wiki.
Supported Boards
NuttX supports a wide variety of platforms. See the full list on the Supported Platforms page.
Contributing
If you wish to contribute to the NuttX project, read the Contributing guidelines for information on Git usage, coding standard, workflow and the NuttX principles.
License
The code in this repository is under either the Apache 2 license, or a license compatible with the Apache 2 license. See the License Page for more information.