From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4dx2MK0QFxz331k for ; Wed, 21 Jan 2026 11:41:01 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (secp384r1 raw public key) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R12" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4dx2MF3fHFz2xSM for ; Wed, 21 Jan 2026 11:40:57 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4dx2MD1L4pz9Z; Wed, 21 Jan 2026 11:40:56 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1768995656; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=5wJ794k6c1UM/TZ2hh458nhPCU6zqogOkp16UgoNRY8=; b=ogXNMoPwN+BCe7gn6rKJd9FZdB7X5tQCq38Fs0/eQKDWg2RLFbayrZ+/yEhmavdv39JIe1 KtDcd0zSMKLMsyCw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1768995656; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=5wJ794k6c1UM/TZ2hh458nhPCU6zqogOkp16UgoNRY8=; b=nVXqZffj4SiXHtCYB7qvdSDtCtIQWlcc3HeA5Vb0LLEZiL4BhjLa/7RLjLnQZVJ8YgUyGi +afktahNtxG4ZbdHtoxicW7wHOsJJIaEZDfwCy5eQ8CYkPBU3rn6nqPsLw29X2EfZBZWxE mSttKJ4RrcCIKeCKvizkEULIRBqnD+7m/wmEUNxbcsk9H6PEMyqp/t41Ops5R8IeDHPYrp m/sTnM8pJSM5laXCachXkkpyuKEOTvISP2VT3RRCpXYsqxN4TLNis3W8aEO+8nQqR20DXn lq1n55+of6ic3adxVTkDeX20RYXl/tYvtUSXt7wcRraKriQA9R6KmyN/y2G6nQ== Message-ID: <7a8fbb24-8de4-4026-bf67-a8041ae2c4f2@ipfire.org> Date: Wed, 21 Jan 2026 12:40:53 +0100 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Subject: Re: Problem with building flash-images with grub-2.14 To: Michael Tremer Cc: "IPFire: Development-List" References: <9a63ce00-429a-4c8a-a2f2-5599c59a294e@ipfire.org> <955702C3-89D1-4529-9B9F-F2E8300F9AD8@ipfire.org> <4D66CDAF-8A41-473B-8A9D-81BE5FFB3AC1@ipfire.org> Content-Language: en-GB From: Adolf Belka In-Reply-To: <4D66CDAF-8A41-473B-8A9D-81BE5FFB3AC1@ipfire.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Michael, On 21/01/2026 11:59, Michael Tremer wrote: > Hello, > > I am not sure whether it is worth trying to revert this commit: > > https://git.ipfire.org/?p=thirdparty/grub.git;a=commitdiff;h=1a5417f39a0ccefcdd5440f2a67f84d2d2e26960 So that is what is checking the thing that is now failing. > > Worst case what could happen is that it won’t boot. That doesn't sound like what we would want to have happen. Looking at the list of major changes or fixes they don't look like anything where we have to have them in place quickly. The current version we have has all the CVE vulnerability fixes in place. So it seems to me okay to wait for now. Will probably end up being a commit fix rather than a new release. Will just have to keep an eye out on that mail thread to see when there is an update. Regards, Adolf. > > -Michael > >> On 20 Jan 2026, at 20:56, Adolf Belka wrote: >> >> Hi Michael, >> >> On 20/01/2026 17:58, Michael Tremer wrote: >>> Hello Adolf, >>> There is something on the GRUB list about this: >>> https://www.mail-archive.com/grub-devel%40gnu.org/msg42915.html? >>> It seems that it is either a bug in the linker or in GRUB, but there does not seem to be a solution. >> >> Interesting that it is only the flash images that fail and not the cdrom. arch Linux have updated to it and I now have it on all my systems and I ran the grub-install and grub-mkconfig successfully for all systems. >> >>> I suppose we will have to wait for a fix from upstream. >> >> No problems. I have also put the grub-btrfs update into the hold category as that was also updated to 2.14 and don't want to cause problem with that. >> >> Regards, >> >> Adolf. >> >>> Best, >>> -Michael >>>> On 20 Jan 2026, at 12:46, Adolf Belka wrote: >>>> >>>> Hi All, >>>> >>>> Grub-2.14 has been released and I have built it. The build was able to be run successfully. >>>> >>>> The build also successfully ran the cdrom stage but it then failed in the flash-images section of the build. >>>> >>>> I reverted grub back to the previous version and flash-images was able to be built without any issues. >>>> >>>> Here is the end of the log showing the error that caused flash-images to fail. >>>> >>>> Any help or suggestions on how to fix this would be greatly appreciated. If more of the flash-images build log is required then I can put it into the IPFire pastebin (it is around 3000 lines). >>>> >>>> ERROR: ld.so: object '/tools_x86_64/lib/libpakfire_preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. >>>> ERROR: ld.so: object '/tools_x86_64/lib/libpakfire_preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. >>>> Root filesystem isn't btrfs, skipping... >>>> ERROR: ld.so: object '/tools_x86_64/lib/libpakfire_preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. >>>> ERROR: ld.so: object '/tools_x86_64/lib/libpakfire_preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. >>>> ERROR: ld.so: object '/tools_x86_64/lib/libpakfire_preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. >>>> ERROR: ld.so: object '/tools_x86_64/lib/libpakfire_preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. >>>> done >>>> # Boot the first kernel by default >>>> chroot /tmp/harddisk grub-set-default 0 >>>> ERROR: ld.so: object '/tools_x86_64/lib/libpakfire_preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. >>>> ERROR: ld.so: object '/tools_x86_64/lib/libpakfire_preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. >>>> ERROR: ld.so: object '/tools_x86_64/lib/libpakfire_preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. >>>> ERROR: ld.so: object '/tools_x86_64/lib/libpakfire_preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. >>>> ERROR: ld.so: object '/tools_x86_64/lib/libpakfire_preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. >>>> ERROR: ld.so: object '/tools_x86_64/lib/libpakfire_preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. >>>> ERROR: ld.so: object '/tools_x86_64/lib/libpakfire_preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. >>>> # Insert the UUID because grub-mkconfig often fails to >>>> # detect that correctly >>>> sed -i /tmp/harddisk/boot/grub/grub.cfg \ >>>> -e "s/root=[A-Za-z0-9\/=-]*/root=UUID=$(blkid -o value -s UUID /dev/mapper/loop0p3)/g" >>>> # Install GRUB >>>> grub-install --force --recheck --no-floppy --target=i386-pc \ >>>> --root-directory=/tmp/harddisk /dev/loop0 >>>> Installing for i386-pc platform. >>>> grub-install: error: `/usr/lib/grub/i386-pc/kernel.img' is miscompiled: its start address is 0x9074 instead of 0x9000: ld.gold bug?. >>>> make: *** [flash-images:157: /usr/src/log/flash-image] Error 1 >>>> >>>> Regards, >>>> >>>> Adolf. >>>> >> >> >