mirror of
https://gitlab.com/buildroot.org/buildroot.git
synced 2026-08-09 17:03:35 -09:00
90b9302e83
Since qt5base was last bumped in8ab4a0a348(package/qt5: bump packages to latest kde submodule versions), the hash for the downloaded tarball has changed: $ make qt5base-source [...] ERROR: expected: 935d01f5c34903ad9e979431cec7a8a59332ed3fc539e639f5ba87e8d6989b9d ERROR: got : 3067c4d84ba9927bfe65bf606c17af082199e0a3b22781fbf9bc6c6bc3de26dd We know the hash was good back when8ab4a0a348was applied, because the tarball has been cached on sources.buildroot.org with the expected hash: $ curl 'https://sources.buildroot.net/qt5base/qtbase-da6e958319e95fe564d3b30c931492dd666bfaff.tar.bz2' 2>/dev/null |sha256sum - 935d01f5c34903ad9e979431cec7a8a59332ed3fc539e639f5ba87e8d6989b9d - But now, the archive generated by the KDE gorge (Gitlab underneath) has another hash (as seen above). This means that the KDE forge (Gitlab) has changed the way it generates archives. So, what's the delta? It turns out that the only changes are about CRLF that were present in the original archive, and are no longer in the new one. It is to be noted that the affected files do not have CRLFS in the repository. It further turns out that the archive was previously generated with .gitattibutes of the main branch ('dev' in Qt repositories), while now they are generated with the .gitattibutes of the commit for which they are generated. Switch to using the git download method for really reproducible archives... Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Sebastian Weyer <sebastian.weyer@smile.fr> Cc: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com> (cherry picked from commit75da04c817) [Peter: adjust for filename/hash used on 2024.02.x] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
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