Ubuntu
glusterfs package

  1. Bug #1991441
  2. Comment #2

Comment 2 for bug 1991441

Revision history for this message
Paride Legovini (paride) wrote :

Thanks Patrick for this bug report, I've been able to reproduce it on a Raspberry Pi 4.

In these cases it is worth checking if the bug is caused by LTO by trying to recompile the package with LTO disabled. This means recompiling the package with

  DEB_BUILD_MAINT_OPTIONS=optimize=-lto

As you recompiled the package already, would you be able to try recompiling it without LTO (i.e. by setting that flag) and report your findings?

If you do so, please check that the build log doesn't show:

  Building with LTO : yes

and that the compiled is not called with the "-flto" flag. For reference see the build log of the package currently in Jammy [1]: you'll find plenty of "-flto" occurrences.

See https://wiki.ubuntu.com/ToolChain/LTO for more information on LTO and on the ways to disable it.

Thanks!

[1] https://launchpadlibrarian.net/582144161/buildlog_ubuntu-jammy-armhf.glusterfs_10.1-1_BUILDING.txt.gz