5e52c28397
On some CPU architecures it's possible to use MMU pages of different sizes, for example on ARC or ARM. And while for user-space applications the page size is supposed to be transparent, there's still some use of that extra information. In particular it's possible to align data structures or code/data sections on page boundary, etc. For these tricks to become possible tools which pack data (think of the linker, like GNU "ld") need to be informed of the page size to be considered. Obviously, there're some sane defaults which are being used most of the time, so we even think about that peculiarity, but when non-default value needs to be used, GNU "ld" accepts 2 properties related to page size: -z common-page-size=XXX -z max-page-size=YYY And while in thery those might be different (but always "common" <= "max"), and that might make sense if we build for some unknown platfrom, in case of Buildroot when we build entire target's filesystem and so know exactly the configuration we're targeting to, we may safely assume "common-page-size"="max-page-size". See a lengthy discussion in this thread [1]. Fixes: http://autobuild.buildroot.net/results/c8b2f331c98453670cd982558144c4fd84674a3d/ (uclibc) http://autobuild.buildroot.net/results/3a22f7aac38145b26c549254b819f87329e7a77e/ (glibc) And while at it, recover use of "XX-page-size" for ARC, as with [2] moving page size selection in the generic code we've got unexpected override for ARC (note "=", but not "+="): --------------------->8-------------------- ARCH_TOOLCHAIN_WRAPPER_OPTS = -matomic --------------------->8-------------------- [1] https://lists.buildroot.org/pipermail/buildroot/2022-July/646176.html [2] https://git.buildroot.net/buildroot/commit/?id=dcb74db89e74e512e36b32cea6f574a1a1ca84c4 Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> |
||
|---|---|---|
| arch | ||
| board | ||
| boot | ||
| configs | ||
| docs | ||
| fs | ||
| linux | ||
| package | ||
| support | ||
| system | ||
| toolchain | ||
| utils | ||
| .clang-format | ||
| .defconfig | ||
| .flake8 | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .shellcheckrc | ||
| CHANGES | ||
| Config.in | ||
| Config.in.legacy | ||
| COPYING | ||
| DEVELOPERS | ||
| Makefile | ||
| Makefile.legacy | ||
| README | ||
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. The documentation can be found in docs/manual. You can generate a text document with 'make manual-text' and read output/docs/manual/manual.text. Online documentation can be found at http://buildroot.org/docs.html To build and use the buildroot stuff, do the following: 1) run 'make menuconfig' 2) select the target architecture and the packages you wish to compile 3) run 'make' 4) wait while it compiles 5) find the kernel, bootloader, root filesystem, etc. in output/images You do not need to be root to build or run buildroot. Have fun! Buildroot comes with a basic configuration for a number of boards. Run 'make list-defconfigs' to view the list of provided configurations. Please feed suggestions, bug reports, insults, and bribes back to the buildroot mailing list: buildroot@buildroot.org You can also find us on #buildroot on OFTC IRC. If you would like to contribute patches, please read https://buildroot.org/manual.html#submitting-patches