[{"data":1,"prerenderedAt":946},["ShallowReactive",2],{"search-index":3,"doc-bootlin-toolchains-arm-riscv-2026":105},[4,9,13,17,21,26,31,36,41,46,51,56,61,66,71,76,81,86,91,96,101],{"_path":5,"title":6,"description":7,"date":8},"/dev/eu-cyber-resilience-act-firmware-evidence-pack","CRA Firmware Evidence: Scope, Dates and Preparation","Practical breakdown of the EU Cyber Resilience Act requirements for embedded firmware teams, covering technical obligations, SBOM requirements, vulnerability handling, and the evidence pack needed for compliance.","2026-04-19T08:00:00.000Z",{"_path":10,"title":11,"description":12,"date":8},"/dev/pkg/firmware-sboms-spdx-cyclonedx-2026","Firmware SBOMs: SPDX, CycloneDX and Publication Workflows","Practical comparison of SPDX and CycloneDX for firmware SBOMs, covering what to include, automation approaches, tooling, and publication strategies for embedded Linux products.",{"_path":14,"title":15,"description":16,"date":8},"/dev/pkg/spdx-3-0-embedded-builds-practical","SPDX 3.0 for Embedded Builds: Packages, Files, and Relationships Engineers Actually Use","Practical guide to SPDX 3.0 for embedded Linux, covering the data model, package and file elements, relationship types, and how to produce useful SPDX documents from Yocto and Buildroot builds.",{"_path":18,"title":19,"description":20,"date":8},"/dev/slsa-build-provenance-firmware-sign-verify","SLSA Build Provenance for Firmware: What to Collect, How to Sign, How to Verify","Practical implementation guide for SLSA build provenance in firmware pipelines, covering provenance generation, signing with Sigstore, verification workflows, and integration with SBOMs.",{"_path":22,"title":23,"description":24,"date":25},"/dev/vex-csaf-embedded-not-affected-scale","VEX and CSAF for Embedded Vulnerability Status","How to produce and distribute VEX documents and CSAF advisories for embedded firmware, enabling downstream consumers to filter false positives from vulnerability scans.","2026-04-15T20:03:00.000Z",{"_path":27,"title":28,"description":29,"date":30},"/dev/yocto-5-2-walnascar-highlights-embedded-2026","Yocto 5.2 Walnascar: Release Changes and Migration Context","Key changes in Yocto 5.2 Walnascar relevant to embedded product teams, covering toolchain updates, security improvements, SPDX 3.0 support, and migration notes.","2026-04-12T08:14:00.000Z",{"_path":32,"title":33,"description":34,"date":35},"/dev/yocto-esdk-faster-iteration-2026","Yocto eSDK in 2026: Faster Application Iteration Without Full Rebuild Cycles","How to use Yocto's extensible SDK to speed up application development by building and testing packages without running full BitBake builds.","2026-04-11T07:09:00.000Z",{"_path":37,"title":38,"description":39,"date":40},"/dev/yocto-layers-maintainable-strategy-2026","Maintaining Yocto Layers: Appends, Forks and Upgrades","Practical guidance on structuring Yocto layers for long-term maintainability, covering layer boundaries, naming conventions, version pinning, and upgrade workflows.","2026-04-07T13:41:00.000Z",{"_path":42,"title":43,"description":44,"date":45},"/doc/bootlin-toolchains-arm-riscv-2026","Bootlin Toolchains in Practice: Picking the Right Prebuilt Toolchain for ARM and RISC-V","How to select and validate Bootlin prebuilt cross-compilation toolchains for ARM Cortex-A, Cortex-M, and RISC-V targets in embedded Linux projects.","2026-03-10T16:05:00.000Z",{"_path":47,"title":48,"description":49,"date":50},"/doc/buildroot-vs-yocto-2026","Buildroot vs Yocto: BSPs, Build Workflow and Maintenance","A detailed comparison of Buildroot and Yocto for embedded Linux, covering build performance, long-term maintenance, layer ecosystems, and practical decision criteria for product teams in 2026.","2026-03-05T08:12:00.000Z",{"_path":52,"title":53,"description":54,"date":55},"/doc/cross-compilation-toolchain-triplet-clib-2026","Cross-Compilation: Target Triplets and glibc vs musl","Practical guidance on selecting cross-compilation toolchains for embedded Linux, understanding target triplets, and choosing between glibc and musl for your production firmware.","2026-03-07T07:43:00.000Z",{"_path":57,"title":58,"description":59,"date":60},"/doc/erofs-vs-squashfs-2026","EROFS vs SquashFS: Compression, Performance and OTA Trade-offs","Detailed comparison of EROFS and SquashFS for embedded Linux in 2026, covering read performance, compression ratios, deduplication, and integration with OTA update schemes.","2026-03-22T14:22:00.000Z",{"_path":62,"title":63,"description":64,"date":65},"/doc/ota-updates-rauc-swupdate-mender-2026","RAUC vs SWUpdate vs Mender: Embedded Linux OTA Compared","Comparison of RAUC, SWUpdate, and Mender for embedded Linux OTA updates, covering update models, rollback strategies, fleet management, and integration with Yocto and Buildroot.","2026-03-28T19:07:00.000Z",{"_path":67,"title":68,"description":69,"date":70},"/doc/plat/device-tree-debugging-overlays-validation-2026","Device Tree Debugging for Embedded Linux: Overlays, Common Errors, and Validation","Practical guide to debugging device tree issues in embedded Linux, covering overlay mechanics, common DTS errors, validation tools, and runtime debugging techniques.","2026-04-05T06:58:00.000Z",{"_path":72,"title":73,"description":74,"date":75},"/doc/plat/porting-checklist-bootloader-kernel-rootfs-2026","Porting Checklist 2026: Bootloader → Kernel → RootFS for New Boards","Complete checklist for porting embedded Linux to a new board, from bootloader bring-up through kernel configuration to root filesystem validation, with practical tips for each stage.","2026-04-02T15:16:00.000Z",{"_path":77,"title":78,"description":79,"date":80},"/doc/real-time-linux-preempt-rt-latency-2026","PREEMPT_RT Linux: Configuration and Cyclictest Latency Tests","Practical guide to PREEMPT_RT on embedded Linux covering kernel configuration, IRQ threading, latency measurement with cyclictest, and tuning techniques with explicit test conditions and interpretation limits.","2026-03-23T05:48:00.000Z",{"_path":82,"title":83,"description":84,"date":85},"/doc/rootfs-integrity-dm-verity-immutable-images","dm-verity for Rootfs Integrity: Design, Trust and Recovery","How to design and implement dm-verity-protected root filesystems for embedded Linux, covering hash tree generation, kernel integration, error handling, and update strategies.","2026-03-19T08:56:00.000Z",{"_path":87,"title":88,"description":89,"date":90},"/doc/rtos-vs-embedded-linux-zephyr-2026","RTOS vs Embedded Linux: Zephyr, FreeRTOS and Linux Compared","Practical comparison of RTOS (Zephyr, FreeRTOS) and embedded Linux for product design, covering latency, memory footprint, ecosystem maturity, and hybrid architectures.","2026-03-30T09:35:00.000Z",{"_path":92,"title":93,"description":94,"date":95},"/doc/secure-boot-uboot-fit-signatures-chain-of-trust","U-Boot Secure Boot: FIT Signatures and Chain of Trust","Understand U-Boot FIT signatures, trusted control device trees and boot-chain limits with a versioned example and explicit rejection and recovery tests.","2026-03-14T06:29:00.000Z",{"_path":97,"title":98,"description":99,"date":100},"/doc/verified-boot-patterns-uboot-keys-failure-modes","Verified Boot Patterns in U-Boot: What to Verify, Where Keys Live, and Failure Modes","Deep dive into U-Boot verified boot patterns covering signature scopes, key storage options, common failure modes, and practical debugging techniques for embedded Linux platforms.","2026-03-16T18:11:00.000Z",{"_path":102,"title":103,"description":104},"/image-manifest","ProteanOS Image Manifest","This document lists all hero and supporting images needed for the website.",{"_path":42,"_dir":106,"_draft":107,"_partial":107,"_locale":108,"title":43,"description":44,"date":45,"lastmod":109,"draft":107,"hero":110,"tags":111,"category":106,"body":115,"_type":940,"_id":941,"_source":942,"_file":943,"_stem":944,"_extension":945},"doc",false,"","2026-11-18T00:00:00.000Z","/images/hero/bootlin-toolchains-arm-riscv-2026-1600x900.jpg",[112,113,114],"Embedded Linux","ProteanOS","Toolchains",{"type":116,"children":117,"toc":919},"root",[118,126,133,138,168,190,196,203,216,235,241,254,271,277,298,315,328,334,339,345,359,383,388,393,398,418,423,457,463,672,683,689,694,746,752,765,771,784,792,798,811,817,829,835,840,863,868,874,879,897,902,908,913],{"type":119,"tag":120,"props":121,"children":122},"element","p",{},[123],{"type":124,"value":125},"text","Choose a Bootlin toolchain that matches your build host, target instruction set, ABI and C library. A prebuilt archive saves the compiler build. Before selecting one, check which kernel headers, sysroot libraries and debugger features the release provides. Compile and inspect a small executable before using the toolchain for an application port.",{"type":119,"tag":127,"props":128,"children":130},"h2",{"id":129},"what-bootlin-provides",[131],{"type":124,"value":132},"What Bootlin provides",{"type":119,"tag":120,"props":134,"children":135},{},[136],{"type":124,"value":137},"Bootlin's toolchain repository offers prebuilt GCC toolchains for a wide range of architectures. Each toolchain is built with a specific combination of:",{"type":119,"tag":139,"props":140,"children":141},"ul",{},[142,148,153,158,163],{"type":119,"tag":143,"props":144,"children":145},"li",{},[146],{"type":124,"value":147},"GCC version (typically tracking the latest stable release)",{"type":119,"tag":143,"props":149,"children":150},{},[151],{"type":124,"value":152},"Binutils version",{"type":119,"tag":143,"props":154,"children":155},{},[156],{"type":124,"value":157},"C library (glibc, musl, or uClibc-ng)",{"type":119,"tag":143,"props":159,"children":160},{},[161],{"type":124,"value":162},"Kernel headers version",{"type":119,"tag":143,"props":164,"children":165},{},[166],{"type":124,"value":167},"Architecture and ABI variant",{"type":119,"tag":120,"props":169,"children":170},{},[171,173,180,182,188],{"type":124,"value":172},"Toolchains are available as compressed tarballs. Extract, set your ",{"type":119,"tag":174,"props":175,"children":177},"code",{"className":176},[],[178],{"type":124,"value":179},"PATH",{"type":124,"value":181}," and ",{"type":119,"tag":174,"props":183,"children":185},{"className":184},[],[186],{"type":124,"value":187},"CROSS_COMPILE",{"type":124,"value":189}," environment variables, and you are ready to build.",{"type":119,"tag":127,"props":191,"children":193},{"id":192},"choosing-by-architecture",[194],{"type":124,"value":195},"Choosing by architecture",{"type":119,"tag":197,"props":198,"children":200},"h3",{"id":199},"arm-cortex-a-32-bit",[201],{"type":124,"value":202},"ARM Cortex-A (32-bit)",{"type":119,"tag":120,"props":204,"children":205},{},[206,208,214],{"type":124,"value":207},"For Cortex-A series processors (A7, A8, A9, A15, A17), you typically need an ",{"type":119,"tag":174,"props":209,"children":211},{"className":210},[],[212],{"type":124,"value":213},"armv7-eabihf",{"type":124,"value":215}," toolchain. The \"hf\" suffix indicates hard-float ABI, which uses the VFP/NEON hardware floating-point unit. All modern Cortex-A parts have hardware floating point; there is no reason to use soft-float on these targets.",{"type":119,"tag":120,"props":217,"children":218},{},[219,221,227,229],{"type":124,"value":220},"Bootlin variant: ",{"type":119,"tag":174,"props":222,"children":224},{"className":223},[],[225],{"type":124,"value":226},"armv7-eabihf--glibc",{"type":124,"value":228}," or ",{"type":119,"tag":174,"props":230,"children":232},{"className":231},[],[233],{"type":124,"value":234},"armv7-eabihf--musl",{"type":119,"tag":197,"props":236,"children":238},{"id":237},"aarch64-64-bit-arm",[239],{"type":124,"value":240},"AArch64 (64-bit ARM)",{"type":119,"tag":120,"props":242,"children":243},{},[244,246,252],{"type":124,"value":245},"For Cortex-A53, A55, A72, A76, and newer cores running in 64-bit mode, use an ",{"type":119,"tag":174,"props":247,"children":249},{"className":248},[],[250],{"type":124,"value":251},"aarch64",{"type":124,"value":253}," toolchain. The ABI is simpler here-there is only one standard ABI for AArch64 Linux.",{"type":119,"tag":120,"props":255,"children":256},{},[257,258,264,265],{"type":124,"value":220},{"type":119,"tag":174,"props":259,"children":261},{"className":260},[],[262],{"type":124,"value":263},"aarch64--glibc",{"type":124,"value":228},{"type":119,"tag":174,"props":266,"children":268},{"className":267},[],[269],{"type":124,"value":270},"aarch64--musl",{"type":119,"tag":197,"props":272,"children":274},{"id":273},"risc-v-64-bit",[275],{"type":124,"value":276},"RISC-V 64-bit",{"type":119,"tag":120,"props":278,"children":279},{},[280,282,288,290,296],{"type":124,"value":281},"RISC-V toolchains need the correct ISA string. The standard Linux configuration is ",{"type":119,"tag":174,"props":283,"children":285},{"className":284},[],[286],{"type":124,"value":287},"rv64gc",{"type":124,"value":289}," (also written ",{"type":119,"tag":174,"props":291,"children":293},{"className":292},[],[294],{"type":124,"value":295},"rv64imafdc",{"type":124,"value":297},"), which includes integer, multiply, atomic, single-float, double-float, and compressed extensions. Most RISC-V Linux-capable SoCs implement this full set.",{"type":119,"tag":120,"props":299,"children":300},{},[301,302,308,309],{"type":124,"value":220},{"type":119,"tag":174,"props":303,"children":305},{"className":304},[],[306],{"type":124,"value":307},"riscv64-lp64d--glibc",{"type":124,"value":228},{"type":119,"tag":174,"props":310,"children":312},{"className":311},[],[313],{"type":124,"value":314},"riscv64-lp64d--musl",{"type":119,"tag":120,"props":316,"children":317},{},[318,320,326],{"type":124,"value":319},"The ",{"type":119,"tag":174,"props":321,"children":323},{"className":322},[],[324],{"type":124,"value":325},"lp64d",{"type":124,"value":327}," ABI indicates 64-bit long/pointer with hardware double-precision float passing.",{"type":119,"tag":197,"props":329,"children":331},{"id":330},"risc-v-32-bit",[332],{"type":124,"value":333},"RISC-V 32-bit",{"type":119,"tag":120,"props":335,"children":336},{},[337],{"type":124,"value":338},"For 32-bit RISC-V targets (less common for Linux, more common for bare-metal or RTOS), the ISA and ABI vary more. Verify your SoC's supported extensions before selecting.",{"type":119,"tag":127,"props":340,"children":342},{"id":341},"choosing-between-glibc-and-musl",[343],{"type":124,"value":344},"Choosing between glibc and musl",{"type":119,"tag":120,"props":346,"children":347},{},[348,350,357],{"type":124,"value":349},"Every Bootlin toolchain is offered in at least two C library variants. The ",{"type":119,"tag":351,"props":352,"children":354},"a",{"href":353},"/doc/cross-compilation-toolchain-triplet-clib-2026/",[355],{"type":124,"value":356},"cross-compilation guide",{"type":124,"value":358}," covers the detailed trade-offs. The short version:",{"type":119,"tag":139,"props":360,"children":361},{},[362,373],{"type":119,"tag":143,"props":363,"children":364},{},[365,371],{"type":119,"tag":366,"props":367,"children":368},"strong",{},[369],{"type":124,"value":370},"glibc",{"type":124,"value":372}," for maximum application compatibility and when rootfs size is not a primary constraint",{"type":119,"tag":143,"props":374,"children":375},{},[376,381],{"type":119,"tag":366,"props":377,"children":378},{},[379],{"type":124,"value":380},"musl",{"type":124,"value":382}," for minimal images, static linking, or when you need deterministic, simple libc behaviour",{"type":119,"tag":120,"props":384,"children":385},{},[386],{"type":124,"value":387},"You cannot mix them. Once you choose a C library for a target, every shared library and application on that target must be built against the same one.",{"type":119,"tag":127,"props":389,"children":391},{"id":390},"kernel-headers-version",[392],{"type":124,"value":162},{"type":119,"tag":120,"props":394,"children":395},{},[396],{"type":124,"value":397},"Each Bootlin toolchain is built against a specific Linux kernel headers version. This determines the newest kernel API your userspace can use. The rule: the toolchain headers version must be less than or equal to the kernel version you deploy.",{"type":119,"tag":120,"props":399,"children":400},{},[401,403,409,410,416],{"type":124,"value":402},"If your product ships Linux 6.1 LTS and the Bootlin toolchain was built with 6.6 headers, userspace may attempt syscalls that 6.1 does not implement. In practice, most applications use well-established syscalls and this is rarely an issue, but it can bite with newer features like ",{"type":119,"tag":174,"props":404,"children":406},{"className":405},[],[407],{"type":124,"value":408},"io_uring",{"type":124,"value":228},{"type":119,"tag":174,"props":411,"children":413},{"className":412},[],[414],{"type":124,"value":415},"landlock",{"type":124,"value":417},".",{"type":119,"tag":120,"props":419,"children":420},{},[421],{"type":124,"value":422},"Check the headers version:",{"type":119,"tag":424,"props":425,"children":429},"pre",{"code":426,"language":427,"meta":108,"className":428,"style":108},"cat ${TOOLCHAIN_PATH}/sysroot/usr/include/linux/version.h\n","bash","language-bash shiki shiki-themes github-dark",[430],{"type":119,"tag":174,"props":431,"children":432},{"__ignoreMap":108},[433],{"type":119,"tag":434,"props":435,"children":438},"span",{"class":436,"line":437},"line",1,[439,445,451],{"type":119,"tag":434,"props":440,"children":442},{"style":441},"--shiki-default:#B392F0",[443],{"type":124,"value":444},"cat",{"type":119,"tag":434,"props":446,"children":448},{"style":447},"--shiki-default:#E1E4E8",[449],{"type":124,"value":450}," ${TOOLCHAIN_PATH}",{"type":119,"tag":434,"props":452,"children":454},{"style":453},"--shiki-default:#9ECBFF",[455],{"type":124,"value":456},"/sysroot/usr/include/linux/version.h\n",{"type":119,"tag":127,"props":458,"children":460},{"id":459},"download-and-setup-workflow",[461],{"type":124,"value":462},"Download and setup workflow",{"type":119,"tag":424,"props":464,"children":466},{"code":465,"language":427,"meta":108,"className":428,"style":108},"# Download (example: AArch64 glibc)\nwget https://toolchains.bootlin.com/downloads/releases/toolchains/aarch64/tarballs/aarch64--glibc--stable-2024.11-1.tar.xz\n\n# Extract\ntar xf aarch64--glibc--stable-2024.11-1.tar.xz\n\n# Set environment\nexport TOOLCHAIN_PATH=$(pwd)/aarch64--glibc--stable-2024.11-1\nexport PATH=${TOOLCHAIN_PATH}/bin:${PATH}\nexport CROSS_COMPILE=aarch64-linux-\n\n# Verify\naarch64-linux-gcc --version\naarch64-linux-gcc -dumpmachine\n",[467],{"type":119,"tag":174,"props":468,"children":469},{"__ignoreMap":108},[470,479,493,503,512,531,539,548,584,606,628,636,645,659],{"type":119,"tag":434,"props":471,"children":472},{"class":436,"line":437},[473],{"type":119,"tag":434,"props":474,"children":476},{"style":475},"--shiki-default:#6A737D",[477],{"type":124,"value":478},"# Download (example: AArch64 glibc)\n",{"type":119,"tag":434,"props":480,"children":482},{"class":436,"line":481},2,[483,488],{"type":119,"tag":434,"props":484,"children":485},{"style":441},[486],{"type":124,"value":487},"wget",{"type":119,"tag":434,"props":489,"children":490},{"style":453},[491],{"type":124,"value":492}," https://toolchains.bootlin.com/downloads/releases/toolchains/aarch64/tarballs/aarch64--glibc--stable-2024.11-1.tar.xz\n",{"type":119,"tag":434,"props":494,"children":496},{"class":436,"line":495},3,[497],{"type":119,"tag":434,"props":498,"children":500},{"emptyLinePlaceholder":499},true,[501],{"type":124,"value":502},"\n",{"type":119,"tag":434,"props":504,"children":506},{"class":436,"line":505},4,[507],{"type":119,"tag":434,"props":508,"children":509},{"style":475},[510],{"type":124,"value":511},"# Extract\n",{"type":119,"tag":434,"props":513,"children":515},{"class":436,"line":514},5,[516,521,526],{"type":119,"tag":434,"props":517,"children":518},{"style":441},[519],{"type":124,"value":520},"tar",{"type":119,"tag":434,"props":522,"children":523},{"style":453},[524],{"type":124,"value":525}," xf",{"type":119,"tag":434,"props":527,"children":528},{"style":453},[529],{"type":124,"value":530}," aarch64--glibc--stable-2024.11-1.tar.xz\n",{"type":119,"tag":434,"props":532,"children":534},{"class":436,"line":533},6,[535],{"type":119,"tag":434,"props":536,"children":537},{"emptyLinePlaceholder":499},[538],{"type":124,"value":502},{"type":119,"tag":434,"props":540,"children":542},{"class":436,"line":541},7,[543],{"type":119,"tag":434,"props":544,"children":545},{"style":475},[546],{"type":124,"value":547},"# Set environment\n",{"type":119,"tag":434,"props":549,"children":551},{"class":436,"line":550},8,[552,558,563,568,573,579],{"type":119,"tag":434,"props":553,"children":555},{"style":554},"--shiki-default:#F97583",[556],{"type":124,"value":557},"export",{"type":119,"tag":434,"props":559,"children":560},{"style":447},[561],{"type":124,"value":562}," TOOLCHAIN_PATH",{"type":119,"tag":434,"props":564,"children":565},{"style":554},[566],{"type":124,"value":567},"=",{"type":119,"tag":434,"props":569,"children":570},{"style":447},[571],{"type":124,"value":572},"$(",{"type":119,"tag":434,"props":574,"children":576},{"style":575},"--shiki-default:#79B8FF",[577],{"type":124,"value":578},"pwd",{"type":119,"tag":434,"props":580,"children":581},{"style":447},[582],{"type":124,"value":583},")/aarch64--glibc--stable-2024.11-1\n",{"type":119,"tag":434,"props":585,"children":587},{"class":436,"line":586},9,[588,592,597,601],{"type":119,"tag":434,"props":589,"children":590},{"style":554},[591],{"type":124,"value":557},{"type":119,"tag":434,"props":593,"children":594},{"style":447},[595],{"type":124,"value":596}," PATH",{"type":119,"tag":434,"props":598,"children":599},{"style":554},[600],{"type":124,"value":567},{"type":119,"tag":434,"props":602,"children":603},{"style":447},[604],{"type":124,"value":605},"${TOOLCHAIN_PATH}/bin:${PATH}\n",{"type":119,"tag":434,"props":607,"children":609},{"class":436,"line":608},10,[610,614,619,623],{"type":119,"tag":434,"props":611,"children":612},{"style":554},[613],{"type":124,"value":557},{"type":119,"tag":434,"props":615,"children":616},{"style":447},[617],{"type":124,"value":618}," CROSS_COMPILE",{"type":119,"tag":434,"props":620,"children":621},{"style":554},[622],{"type":124,"value":567},{"type":119,"tag":434,"props":624,"children":625},{"style":447},[626],{"type":124,"value":627},"aarch64-linux-\n",{"type":119,"tag":434,"props":629,"children":631},{"class":436,"line":630},11,[632],{"type":119,"tag":434,"props":633,"children":634},{"emptyLinePlaceholder":499},[635],{"type":124,"value":502},{"type":119,"tag":434,"props":637,"children":639},{"class":436,"line":638},12,[640],{"type":119,"tag":434,"props":641,"children":642},{"style":475},[643],{"type":124,"value":644},"# Verify\n",{"type":119,"tag":434,"props":646,"children":648},{"class":436,"line":647},13,[649,654],{"type":119,"tag":434,"props":650,"children":651},{"style":441},[652],{"type":124,"value":653},"aarch64-linux-gcc",{"type":119,"tag":434,"props":655,"children":656},{"style":575},[657],{"type":124,"value":658}," --version\n",{"type":119,"tag":434,"props":660,"children":662},{"class":436,"line":661},14,[663,667],{"type":119,"tag":434,"props":664,"children":665},{"style":441},[666],{"type":124,"value":653},{"type":119,"tag":434,"props":668,"children":669},{"style":575},[670],{"type":124,"value":671}," -dumpmachine\n",{"type":119,"tag":120,"props":673,"children":674},{},[675,676,681],{"type":124,"value":319},{"type":119,"tag":174,"props":677,"children":679},{"className":678},[],[680],{"type":124,"value":187},{"type":124,"value":682}," prefix is what kernel and U-Boot Makefiles expect. Set it once in your shell or build script.",{"type":119,"tag":127,"props":684,"children":686},{"id":685},"validation-checklist",[687],{"type":124,"value":688},"Validation checklist",{"type":119,"tag":120,"props":690,"children":691},{},[692],{"type":124,"value":693},"Before committing to a toolchain for production use:",{"type":119,"tag":695,"props":696,"children":697},"ol",{},[698,708,718,736],{"type":119,"tag":143,"props":699,"children":700},{},[701,706],{"type":119,"tag":366,"props":702,"children":703},{},[704],{"type":124,"value":705},"Build the kernel:",{"type":124,"value":707}," Compile your target kernel with the toolchain. Boot it on hardware or QEMU. A kernel build exercises the assembler, compiler, and linker thoroughly.",{"type":119,"tag":143,"props":709,"children":710},{},[711,716],{"type":119,"tag":366,"props":712,"children":713},{},[714],{"type":124,"value":715},"Build a minimal userspace:",{"type":124,"value":717}," Compile BusyBox or a simple init program. Run it on target. This validates the C library and dynamic linker.",{"type":119,"tag":143,"props":719,"children":720},{},[721,726,728,734],{"type":119,"tag":366,"props":722,"children":723},{},[724],{"type":124,"value":725},"Check ABI consistency:",{"type":124,"value":727}," Use ",{"type":119,"tag":174,"props":729,"children":731},{"className":730},[],[732],{"type":124,"value":733},"readelf -A",{"type":124,"value":735}," on a compiled binary and verify the ABI flags match your target hardware.",{"type":119,"tag":143,"props":737,"children":738},{},[739,744],{"type":119,"tag":366,"props":740,"children":741},{},[742],{"type":124,"value":743},"Run the test suite",{"type":124,"value":745}," (optional but recommended): Bootlin runs toolchain test suites before release, but running your own application-specific tests catches integration issues early.",{"type":119,"tag":127,"props":747,"children":749},{"id":748},"using-bootlin-toolchains-with-build-systems",[750],{"type":124,"value":751},"Using Bootlin toolchains with build systems",{"type":119,"tag":120,"props":753,"children":754},{},[755,757,763],{"type":124,"value":756},"If the build system is still undecided, compare ",{"type":119,"tag":351,"props":758,"children":760},{"href":759},"/doc/buildroot-vs-yocto-2026/",[761],{"type":124,"value":762},"Buildroot vs Yocto",{"type":124,"value":764}," before choosing an external toolchain. Confirm that the selected BSP and libc combination are supported.",{"type":119,"tag":197,"props":766,"children":768},{"id":767},"with-buildroot",[769],{"type":124,"value":770},"With Buildroot",{"type":119,"tag":120,"props":772,"children":773},{},[774,776,782],{"type":124,"value":775},"Buildroot has native support for external toolchains. In your ",{"type":119,"tag":174,"props":777,"children":779},{"className":778},[],[780],{"type":124,"value":781},".config",{"type":124,"value":783},":",{"type":119,"tag":424,"props":785,"children":787},{"code":786},"BR2_TOOLCHAIN_EXTERNAL=y\nBR2_TOOLCHAIN_EXTERNAL_CUSTOM=y\nBR2_TOOLCHAIN_EXTERNAL_PATH=\"/path/to/aarch64--glibc--stable-2024.11-1\"\nBR2_TOOLCHAIN_EXTERNAL_PREFIX=\"aarch64-linux\"\n",[788],{"type":119,"tag":174,"props":789,"children":790},{"__ignoreMap":108},[791],{"type":124,"value":786},{"type":119,"tag":197,"props":793,"children":795},{"id":794},"with-yocto",[796],{"type":124,"value":797},"With Yocto",{"type":119,"tag":120,"props":799,"children":800},{},[801,803,809],{"type":124,"value":802},"Yocto can use external toolchains through meta-sourcery or by configuring the ",{"type":119,"tag":174,"props":804,"children":806},{"className":805},[],[807],{"type":124,"value":808},"EXTERNAL_TOOLCHAIN",{"type":124,"value":810}," variable. This bypasses Yocto's native toolchain build, saving significant build time.",{"type":119,"tag":197,"props":812,"children":814},{"id":813},"with-proteanos-prokit",[815],{"type":124,"value":816},"With ProteanOS ProKit",{"type":119,"tag":120,"props":818,"children":819},{},[820,821,827],{"type":124,"value":319},{"type":119,"tag":351,"props":822,"children":824},{"href":823},"/dev/prokit/",[825],{"type":124,"value":826},"ProKit documentation",{"type":124,"value":828}," explains how to configure the toolchain path for ProteanOS builds. ProKit detects the toolchain's target triplet and C library automatically from the compiler's self-reported configuration.",{"type":119,"tag":127,"props":830,"children":832},{"id":831},"updating-toolchains",[833],{"type":124,"value":834},"Updating toolchains",{"type":119,"tag":120,"props":836,"children":837},{},[838],{"type":124,"value":839},"Bootlin releases updated toolchains regularly, tracking upstream GCC and binutils releases. When updating:",{"type":119,"tag":695,"props":841,"children":842},{},[843,848,853,858],{"type":119,"tag":143,"props":844,"children":845},{},[846],{"type":124,"value":847},"Download the new toolchain version",{"type":119,"tag":143,"props":849,"children":850},{},[851],{"type":124,"value":852},"Rebuild your entire image (kernel + rootfs) with the new toolchain",{"type":119,"tag":143,"props":854,"children":855},{},[856],{"type":124,"value":857},"Run your full test suite on target hardware",{"type":119,"tag":143,"props":859,"children":860},{},[861],{"type":124,"value":862},"Document the toolchain version in your build configuration",{"type":119,"tag":120,"props":864,"children":865},{},[866],{"type":124,"value":867},"Do not mix object files compiled with different toolchain versions in the same image. The C library version must be consistent across all userspace components.",{"type":119,"tag":127,"props":869,"children":871},{"id":870},"when-bootlin-toolchains-are-not-enough",[872],{"type":124,"value":873},"When Bootlin toolchains are not enough",{"type":119,"tag":120,"props":875,"children":876},{},[877],{"type":124,"value":878},"Bootlin covers the most common architecture and ABI combinations, but you may need a custom toolchain when:",{"type":119,"tag":139,"props":880,"children":881},{},[882,887,892],{"type":119,"tag":143,"props":883,"children":884},{},[885],{"type":124,"value":886},"Your target uses a non-standard ISA extension set (e.g., RISC-V with vector extensions)",{"type":119,"tag":143,"props":888,"children":889},{},[890],{"type":124,"value":891},"You need a specific GCC version for a compiler bug workaround",{"type":119,"tag":143,"props":893,"children":894},{},[895],{"type":124,"value":896},"Your organisation requires toolchain provenance documentation for certification",{"type":119,"tag":120,"props":898,"children":899},{},[900],{"type":124,"value":901},"In these cases, crosstool-NG or your build system's native toolchain builder is the right approach. The board bring-up documentation covers toolchain selection as part of the broader board bring-up process.",{"type":119,"tag":127,"props":903,"children":905},{"id":904},"summary",[906],{"type":124,"value":907},"Summary",{"type":119,"tag":120,"props":909,"children":910},{},[911],{"type":124,"value":912},"Bootlin prebuilt toolchains eliminate one of the most time-consuming steps in embedded Linux development. Choose based on your target architecture, C library preference, and kernel headers version. Validate thoroughly before production use, and treat toolchain updates as first-class milestones in your release process.",{"type":119,"tag":914,"props":915,"children":916},"style",{},[917],{"type":124,"value":918},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"title":108,"searchDepth":481,"depth":481,"links":920},[921,922,928,929,930,931,932,937,938,939],{"id":129,"depth":481,"text":132},{"id":192,"depth":481,"text":195,"children":923},[924,925,926,927],{"id":199,"depth":495,"text":202},{"id":237,"depth":495,"text":240},{"id":273,"depth":495,"text":276},{"id":330,"depth":495,"text":333},{"id":341,"depth":481,"text":344},{"id":390,"depth":481,"text":162},{"id":459,"depth":481,"text":462},{"id":685,"depth":481,"text":688},{"id":748,"depth":481,"text":751,"children":933},[934,935,936],{"id":767,"depth":495,"text":770},{"id":794,"depth":495,"text":797},{"id":813,"depth":495,"text":816},{"id":831,"depth":481,"text":834},{"id":870,"depth":481,"text":873},{"id":904,"depth":481,"text":907},"markdown","content:doc:bootlin-toolchains-arm-riscv-2026.md","content","doc/bootlin-toolchains-arm-riscv-2026.md","doc/bootlin-toolchains-arm-riscv-2026","md",1795338687473]