public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: Michael Tremer <michael.tremer@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: Problem with building flash-images with grub-2.14
Date: Tue, 20 Jan 2026 21:56:13 +0100	[thread overview]
Message-ID: <a52aa92b-f350-48b5-a8d3-9c080efadad8@ipfire.org> (raw)
In-Reply-To: <955702C3-89D1-4529-9B9F-F2E8300F9AD8@ipfire.org>

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 <adolf.belka@ipfire.org> 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.
>>
> 



  reply	other threads:[~2026-01-20 20:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 12:46 Adolf Belka
2026-01-20 16:58 ` Michael Tremer
2026-01-20 20:56   ` Adolf Belka [this message]
2026-01-21 10:59     ` Michael Tremer
2026-01-21 11:40       ` Adolf Belka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a52aa92b-f350-48b5-a8d3-9c080efadad8@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    --cc=michael.tremer@ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox