1DOLLY 32MODULE bootstrap34# This is the first step. It has no requirements: its exact compiler commands5# and C headers are the externally supplied bootstrap seed. How those headers6# eventually map to the lower-level machine contract is deliberately open.7SOURCE HOST /include/dolly/toolchain.h /usr/include/dolly/toolchain.h 6f9da3258e970e356c31034e1f109a04ac8bd5ab57dc82c19aebf293289fb4158SOURCE HOST /include/dolly/runtime.h   /usr/include/dolly/runtime.h   060f61049f36cec927ca4560a53f870c0af08052d5e7506981f5e61657873b719SOURCE HOST /include/dolly/process.h   /usr/include/dolly/process.h   e68de1cbda1fd87eb265128fdfc13313e9498d25316134c55e847e092f20094110SOURCE HOST /include/dolly/http.h      /usr/include/dolly/http.h      7e003122545cd86a44daef371ed15ea9f323dc277e1a9ce9fa4dcd74fc0c6d6411SOURCE HOST /include/dolly/display.h   /usr/include/dolly/display.h   f6cb60e0b7d53286cb4af0b728bf2f460a2993a0f8c5f72c9d7a97386cd1cf4812SOURCE HOST /include/dolly/download.h  /usr/include/dolly/download.h  8924a3e4c82183c2840f9734dcca8a2427b085c5e004d32c90496f926246cc891314EXPORTS HEADER libc      /usr/include15EXPORTS HEADER toolchain /usr/include/dolly/toolchain.h16EXPORTS HEADER runtime   /usr/include/dolly/runtime.h17EXPORTS HEADER process   /usr/include/dolly/process.h18EXPORTS HEADER http      /usr/include/dolly/http.h19EXPORTS HEADER display   /usr/include/dolly/display.h20EXPORTS HEADER download  /usr/include/dolly/download.h2122EXPORTS LIB compiler-rt /usr/lib/libclang_rt.builtins.a2324# These are the complete externally seeded compiler dependencies, not ambient25# additions to every boot. Images retain them by re-exporting these objects.26EXPORTS FOLDER process-sdk       /usr/lib/dolly/process27EXPORTS FOLDER clang-headers     /usr/lib/clang/24/include28EXPORTS FILE   compiler          /usr/libexec/dolly/process-bin/compiler29EXPORTS FILE   kernel-plugin-abi /usr/lib/dolly/dolly-kernel-plugin-0.wasm3031EXPORTS ENV CC    cc32EXPORTS ENV AR    ar33EXPORTS ENV SHELL /bin/slop34EXPORTS ENV PATH  /bin:/usr/bin3536# These programs are linked against the seeded process adapter, so their37# complete input identity is the runtime build ID rather than this recipe38# alone. They are still validated as dolly-process-0 executables when loaded.39EXPORTS TOOL cc40EXPORTS TOOL c++41EXPORTS TOOL ld42EXPORTS TOOL ar43EXPORTS TOOL slop44EXPORTS TOOL dollyfile45EXPORTS TOOL mkdir46EXPORTS TOOL rm47