Follow-up Comment #24, bug #64421 (project groff):

Hello!

With the help from the package maintainer Tobias Powalowski, I was able to
reproduce the broken build locally.  When I build with the `makepkg` tool, the
resulting binary *does not* have the bug.  When I build with the "reproducible
build" approach as explained in
https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot#Convenience_way,
then the resulting binary *does* have the bug.

To build a binary which has the bug, do:

* Check out the Arch Linux package as explained on previous comment and cd to
the directory with the PKGBUILD file.
* Run "extra-x86_64-build" to build it in a fresh chroot

I attached the package with and without the bug in the file
good-and-bad-groff.tar below.  The subfolders "good" and "buggy" contain the
binary package in the working and buggy versions.  These package files can be
extracted with GNU tar using:


tar --zstd -x -f groff-1.23.0-3-x86_64.pkg.tar.zst 


I also included the log files from the two builds.  The compiler options are
logged there as part of the ./configure run.  The flags differ, but not much:

The working package used:


 C compiler and options           : gcc -march=x86-64 -mtune=generic -O2 -pipe
-fno-plt -fexceptions         -Wp,-D_FORTIFY_SOURCE=2 -Wformat
-Werror=format-security         -fstack-clash-protection -fcf-protection 


The buggy package used:


 C compiler and options           : gcc -march=x86-64 -mtune=generic -O2 -pipe
-fno-plt -fexceptions         -Wp,
-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security        
-fstack-clash-protection -fcf-protection -g
-ffile-prefix-map=/build/groff/src=/usr/src/debug/groff -flto=auto 


Surprisingly it is the build which had the bug which has an additional -g
flag. (But it's possible that the debug symbols were stripped after the build
step, to produce separate packages for the binaries and debug symbols)

Another thing that looks suspicious is -flto=auto.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64421>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/


Reply via email to