linux/poky.git/meta/recipes-devtools/syslinux, branch master

The poky repository master branch is no longer being updated.

2025-11-07T13:31:53+00:00

You can either: a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs b) use the new bitbake-setup You can find information about either approach in our documentation: https://docs.yoctoproject.org/ Note that "poky" the distro setting is still available in meta-yocto as before and we continue to use and maintain that. Long live Poky! Some further information on the background of this change can be found in: https://lists.openembedded.org/g/openembedded-architecture/message/2179 Signed-off-by: Richard Purdie

syslinux: Pin to using GCC toolchain

2025-05-22T13:36:49+00:00

It does not compile with clang due to include_next stdarg.h not working as the system expects to match gcc behavior (From OE-Core rev: 4ef959f37816f23e4ed57a71cb9a42fd818aa1fb) Signed-off-by: Khem Raj Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

recipes: Drop remaining md5sum checksums

2025-05-01T13:22:53+00:00

We have long since obsoleted md5sum in favour of sha256sum. Drop the remaining 56 entries (which were showing many recipes hadn't been touched in a long time). They all do have the corresponding sha256sum entries as is clear from the diff. (From OE-Core rev: 7e4bfcc9706fa8a09f6a0004174a2c3b21c90df3) Signed-off-by: Richard Purdie

syslinux: improve isohybrid to process extra sector count for ISO 9660 image

2025-04-29T08:59:01+00:00

Due to commit [cdrtools-native: fix booting EFI ISO live failed] applied to improve mkisofs to fix nsectors exceeds 0xffff situation which set selection criteria type = 2 and save extra nsectors to vendor unique selection criteria In following case, add 64MB extra space to bootable image efi.img, and the partition table of EFI is truncated to 32M $ echo 'IMAGE_FSTYPES:pn-core-image-minimal = " live"' >> conf/local.conf $ echo 'MACHINE_FEATURES:append = " efi pcbios"' >> conf/local.conf $ echo '# 64MB extra space to bootable image efi.img' >> conf/local.conf $ echo 'BOOTIMG_EXTRA_SPACE = "65535"' >> conf/local.conf $ bitbake core-image-minimal $ fdisk -l tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.rootfs.iso ... Device Boot Start End Sectors Size Id Type tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.rootfs.iso1 * 0 376831 376832 184M 0 Empty tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.rootfs.iso2 120 65654 65535 32M ef EFI (FAT-12/16/32) After applying this patch to process extra sector count, the partition table of EFI is 90.3M $ fdisk -l tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.rootfs.iso ... Device Boot Start End Sectors Size Id Type tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.rootfs.iso1 * 0 376831 376832 184M 0 Empty tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.rootfs.iso2 120 185151 185032 90.3M ef EFI (FAT-12/16/32) [1]https://pdos.csail.mit.edu/6.828/2017/readings/boot-cdrom.pdf (From OE-Core rev: b4e112ed7e6ba5a6c6df530d696485a588831851) Signed-off-by: Hongxu Jia Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

syslinux: Use -idirafter to add back path for system stdarg.h

2025-03-27T11:19:04+00:00

syslinux uses -nostdinc to build freestanding, which makes sense, however it also tried to latch its own copy of stdarg.h to include system stdarg.h via "include_next" compiler magic, so it poses to provide own stdarg.h but then secretly include system version behind the scenes :) It uses -nostdinc -iwithprefix include hoping that gcc is uses and gcc has its include-fixed abstraction which also contains stdarg.h so in the end it will find a version of stdarg.h from system (even though it is from the compiler install ) and things will work. On musl, include-fixed is not expected and system includes are simplified so that everyone can look into /usr/include to find them. This can throw syslinux compilation into problems as now it does not find the header from -iprefix and ends up with errors like /mnt/b/yoe/master/sources/poky/build/tmp/work/core2-32-poky-linux-musl/syslinux/6.04-pre2/syslinux-6.04-pre2/com32/lib/../include/stdarg.h:9:15: fatal error: stdarg.h: No such file or directory 9 | #include_next | ^~~~~~~~~~ compilation terminated. Therefore, we use -idirafter to point it into target sysroot as fallback for system headers if it needs them, its added at the very last in search order. It also keeps working with glibc based toolchains as usual and also works with musl toolchains. (From OE-Core rev: 40413233429ceb902d8eb30ccc56aa7a182db772) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

e2fsprogs: upgrade 1.47.0 -> 1.47.1

2024-08-23T08:12:37+00:00

(From OE-Core rev: 4845c854722bc26ae3667a54288d82c043b7e740) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

native/nativesdk: Stop overriding unprefixed *FLAGS variables

2024-07-01T12:58:08+00:00

We're currently encouraging an "arms race" with the FLAGS variables since a recipe might want to set a specific flag for all variants but to do so, += won't work due to the assignment in the native/nativesdk class files. This means recipes are using append. Since the default variables are constructed out of TARGET_XXX variables and we redefine these, there is no need to re-define the un-prefixed variables. If we drop that, the += appends and similar work and recipes don't have to resort to append. Change the classes and cleanup a number of recipes to adapt to the change. This change will result in some flags appearing to some native/nativesdk variants but that is probably what was originally expected anyway. (From OE-Core rev: a157b2f9d93428ca21265cc860a3b58b3698b3aa) Signed-off-by: Richard Purdie

syslinux: Disable error on implicit-function-declaration

2024-02-05T14:06:10+00:00

syslinux has vendored copy of ext2fs/ext2_fs.h but uses ext2fs/ext2fs.h from e2fsprogs package, however, ext2fs/ext2fs.h has dependencies on ext2fs/ext2_fs.h coming from e2fsprogs package as these both headers come from same package, here syslinux uses ext2fs.h from e2fsprogs but supplies its own copy of ext2_fs.h which maybe out of sync and that results in warnings about implicit implicit-function-declarations e.g. recipe-sysroot/usr/include/ext2fs/ext2fs.h:727:16: error: implicit declaration of function 'ext2fs_has_feature_gdt_csum' [-Wimplicit-function-declaration] | 727 | ext2fs_has_feature_gdt_csum(fs->super); | | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ ext2fs_has_feature_gdt_csum here comes from newer version of ext2fs/ext2_fs.h but missing from vendored copy, hence the warning. With gcc-14 this warning is treated as error by default, which breaks the build, so lets treat it as warning only. All these functions are never used in syslinux, so functionality-wise we are fine. (From OE-Core rev: a2b30108055e68b62fdad7319d7d569bc38a07b4) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

syslinux: Allow mtools to be optional

2024-01-10T17:01:28+00:00

Adds a PACKAGECONFIG to syslinux to determine if the mtools version of the utilities is installed or not. The difference between the two versions is that the mtools version can be used by any user with write permission, while the non-mtools can only be used by root. The syslinux-nomtools package is removed, as it was empty and doesn't appear to be used anyway (From OE-Core rev: 06da552733091bc8d332bb932c86cbc8362d44b9) Signed-off-by: Joshua Watt Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

recipes: Drop remaining PR values from recipes

2023-09-22T06:45:17+00:00

We've been removing PR values from recipes at upgrade time for a while. In general anyone maintaining a binary distro would end up having to curate these themselves so the values in OE-Core aren't really that useful anymore. In many ways it makes sense to clear out the remaining ones (which are mostly for 'config' recipes that are unlikely to increase in PV) and leave a clean slate for anyone implementing a binary distro config. References are left in meta-selftest since the tests there do involve them and their removal upon upgrade. (From OE-Core rev: d4c346e8ab8f3cae25d1b01c7331ed9f6d4f96ef) Signed-off-by: Richard Purdie