On Mon, 28 Oct 2024 17:06:11 +0100 Steffen Nurpmeso <stef...@sdaoden.eu> wrote:
> Natanael Copa wrote in > <20241028142621.157769-1-nc...@alpinelinux.org>: > |Fix bug introduced in busybox 1.37.0 that broke kernel builds. > | > |Fixes commit e2287f99fe6f (od: for !DESKTOP, match output more closely > |to GNU coreutils 9.1, implement -s) > > ok, but, for whatever reason and whats it worth, i *really* have > that busybox.static from April 20th which shows the same error > that you had posted on the AlpineLinux list. It may be i mv(1)d > over it, but i do not fiddle with file times and stat(1) says > > Access: 2024-10-28 15:33:22.617028884 +0100 > Modify: 2024-04-20 23:30:27.306450375 +0200 > Change: 2024-04-20 23:30:27.306450375 +0200 > Birth: 2021-07-15 17:15:04.220127694 +0200 > > so i do not think that i did that. You mean this? > $ busybox.static | sed '2,$d' > BusyBox v1.37.0.git (2024-04-20 23:25:28 CEST) multi-call binary I don't know how or where you got that binary from, but I belive the issue was introduced in 1.37.0. -nc _______________________________________________ busybox mailing list busybox@busybox.net https://lists.busybox.net/mailman/listinfo/busybox
