staging/neocturne/tools/Makefile, branch main

tools: remove kernel2minor

2024-06-05T15:03:24Z

Since the Yafut tool is now used for both updating the kernel on MikroTik devices with NAND flash and preparing firmware images for MikroTik devices with NOR flash, remove the kernel2minor utility from the tree as it is no longer used for anything. Signed-off-by: Michał Kępień Link: https://github.com/openwrt/openwrt/pull/13453 Signed-off-by: Robert Marko

mikrotik: switch to Yafut for building MikroTik NOR images

2024-06-05T15:03:24Z

The Yafut tool now has limited capabilities for working on filesystem images stored in regular files. This enables preparing Yaffs2 images for devices with NOR flash using upstream Yaffs2 filesystem code instead of the custom kernel2minor tool. Since minimizing the size of the resulting filesystem image size is important and upstream Yaffs2 code requires two allocator reserve blocks to be available when writing a file to the filesystem, a trick is employed while preparing an OpenWRT image: the blank filesystem image that Yafut operates on initially contains two extra erase blocks that are chopped off after the kernel file is written. This is safe to do because Yaffs2 has a true log structure and therefore only ever writes sequentially (and the size of the kernel file is known beforehand). While the two extra erase blocks are necessary for writes, Yaffs2 code seems to be perfectly capable of reading back files from a "truncated" filesystem that does not contain these extra erase blocks. In terms of image size, this new approach is only marginally worse than the current kernel2minor-based one: specifically, upstream Yaffs2 code needs to write three object headers (each of which takes up an entire data chunk) when the kernel file is written to the filesystem: - an object header for the kernel file when it is created, - an object header for the root directory when the kernel file is created, - an updated object header for the kernel file when the latter is fully written (so that its new size can be recorded). kernel2minor only writes two of these headers, which is the absolute minimum required for reading the file back. This means that the Yafut-based approach causes firmware images to be at most one erase block (64 kB) larger than those created using kernel2minor, but only in the very unfortunate scenario where the size of the kernel file is really close to a multiple of the erase block size. The rest of the calculations performed when the empty filesystem image is first prepared stems from the Yaffs2 layout used by MikroTik NOR devices: each 65,536-byte erase block contains 63 chunks, each of which consists of 1024 bytes of data followed by 16-byte Yaffs tags without ECC data; each such group of 63 chunks is then followed by 16 bytes of padding, which translates to "-C 1040 -B 64k -E" in the Yafut invocation. Yaffs2 checkpoints and summaries are disabled (using Yafut's -P and -S switches, respectively) as they are merely performance optimizations that require extra storage space. The -L and -M switches are used to force little-endian or big-endian byte order (respectively) in the resulting filesystem image, no matter what byte order the build host uses. The tr invocation is used to ensure that the filesystem image is initialized with 0xFF bytes (which are an indicator of unused space for Yaffs2 code). Signed-off-by: Michał Kępień Link: https://github.com/openwrt/openwrt/pull/13453 Signed-off-by: Robert Marko

tools: rework tools-core dependecies

2024-04-06T09:24:18Z

ZSTD and libdeflate do not depend on SED nor flock, so instead of the whole for loop that will filter 2 out of 4 core packages just specify that patch and tar depend on sed explicitly. ZSTD now depends on libdeflate since libdeflate-gzip will then be used to unpack ZSTD as well as most tool archives. Signed-off-by: Rosen Penev Signed-off-by: Robert Marko

tools: make zstd tool core and xz tool non-core

2024-04-06T09:24:18Z

Make zstd tool core and xz tool non-core since zstd is the new default for compression format. Signed-off-by: Christian Marangi

tools: zstd: convert to make and drop meson dependency

2024-04-06T09:24:18Z

Convert to make and drop meson dependency since it's not a core tools and can't depend on advanced build system like cmake or meson. On top of this make is the official build support and cmake/meson are supported by 3rd parties. Signed-off-by: Christian Marangi

tools: add util-linux

2024-03-11T19:17:25Z

since kernel 6.4, commit bca2f3a9406b ("efi/zboot: Add BSS padding before compression") introduces the use of hexdump to padding the EFI kernel binary before compression. util-linux which containing hexdump should then be compiled as a host tool to guarantee not breaking the kernel build process. Signed-off-by: Weijie Gao

tools/elfutils: add missing dependency to fix build error

2023-10-30T08:08:39Z

Signed-off-by: Felix Fietkau

elfutils: fix build and enable on non-linux systems

2023-10-29T14:56:46Z

Use gnulib for compatibility Signed-off-by: Felix Fietkau

tools: add mold, a modern linker

2023-07-04T18:25:40Z

mold is a faster drop-in replacement for existing Unix linkers. A single binary is able to link various targets, which is why this lives in tools/. All toolchain builds then just need to copy the linker over, hence avoiding multiple builds with the same outcome. Signed-off-by: Andre Heider

tools/coreutils: bootstrap to local gnulib source

2023-05-04T04:07:30Z

Using the local gnulib source during bootstrap allows for fine-grained control over the macros and source files for use with coreutils but part of gnulib instead of coreutils, without having to wait for a release or deal with gnulib as a git submodule. In this case, the execution of autotools must be skipped by force. Autoconf and Automake during bootstrap on coreutils only works right when using directly checked-out source. There is a symbol in gnulib, @GNULIB_TIME@ that is not yet defined in coreutils source, so we use the backup of lib/time.in.h instead of the one provided by gnulib source. Signed-off-by: Michael Pratt