There's a thread about it now on Fedora devel list:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/7VI4VFM2AKYTGPOQIZ6IMMYNJW6T2KQF/#7VI4VFM2AKYTGPOQIZ6IMMYNJW6T2KQF

This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Hi guys,
Thank you Zdenek for bringing this to my attention. I will return to this when i will have time to investigate.

it works for me in f32 but breaks in rawhide. It looks like __brp_strip_lto is used for stripping in rawhide. 

set %global __brp_strip_lto %{nil} to the specfile resolves this issue

Hi gdb maintainers,
recently you re-enabled support for guile in gdb which is great but i think that by an accident you enabled it even
for gdb-minimal. Because you added BuildRequires: guile-devel, libguile is present during build and so gdb enables
its support by default [0] "Done by default if libguile is present and found at configure time." and it must be explicitly disabled.
Attempts to boot guile with /usr/share/gdb/guile/gdb/boot.scm which is present only in gdb-headless package then results
in those errors we are now seeing in build logs. I do not think that we need guile support in gdb-minimal.
Solution is quite simple: just add "--without-guile" to GDB_MINIMAL_CONFIGURE_FLAGS.

########################## HOW TO REPRODUCE ##############################################
On fedora rawhide without gdb-headless package
# dnf install gdb-minimal
# gdb-add-index ./executable_with_debuginfo
####### EXPECTED RESULT
No error messages
####### ACTUAL RESULT
Exception caught while booting Guile.
Error in function "open-file":
No such file or directory: "/usr/share/gdb/guile/gdb/boot.scm"
/usr/bin/gdb.minimal: warning: Could not complete Guile gdb module initialization from:
/usr/share/gdb/guile/gdb/boot.scm.
Limited Guile support is available.
Suggest passing --data-directory=/path/to/gdb/data-directory.
##########################################################################################

[0] - https://sourceware.org/gdb/current/onlinedocs/gdb/Configure-Options.html

Thanks for the report.  I've pushed a new GDB that fixes this, both on Rawhide and F32.

I still encountered an exception/warning messages during build kitty:

extracting debug info from /builddir/build/BUILDROOT/kitty-0.16.0-2.fc32.x86_64/usr/lib64/kitty/kittens/diff/diff_speedup.so
extracting debug info from /builddir/build/BUILDROOT/kitty-0.16.0-2.fc32.x86_64/usr/lib64/kitty/kitty/fast_data_types.so
extracting debug info from /builddir/build/BUILDROOT/kitty-0.16.0-2.fc32.x86_64/usr/lib64/kitty/kitty/glfw-wayland.so
extracting debug info from /builddir/build/BUILDROOT/kitty-0.16.0-2.fc32.x86_64/usr/lib64/kitty/kitty/glfw-x11.so
Exception caught while booting Guile.
/usr/bin/gdb.minimal: warning: Could not complete Guile gdb module initialization from:
/usr/share/gdb/guile/gdb/boot.scm.
Limited Guile support is available.
Suggest passing --data-directory=/path/to/gdb/data-directory.
Exception caught while booting Guile.
/usr/bin/gdb.minimal: warning: Could not complete Guile gdb module initialization from:
/usr/share/gdb/guile/gdb/boot.scm.
Limited Guile support is available.
Suggest passing --data-directory=/path/to/gdb/data-directory.
Exception caught while booting Guile.
/usr/bin/gdb.minimal: warning: Could not complete Guile gdb module initialization from:
/usr/share/gdb/guile/gdb/boot.scm.
Limited Guile support is available.
Suggest passing --data-directory=/path/to/gdb/data-directory.
Exception caught while booting Guile.
/usr/bin/gdb.minimal: warning: Could not complete Guile gdb module initialization from:
/usr/share/gdb/guile/gdb/boot.scm.
Limited Guile support is available.
Suggest passing --data-directory=/path/to/gdb/data-directory.
Error in function "open-file":
No such file or directory: "/usr/share/gdb/guile/gdb/boot.scm"gdb-add-index: No index was created for /builddir/build/BUILDROOT/kitty-0.16.0-2.fc32.x86_64/usr/bin/kitty
gdb-add-index: [Was there no debuginfo? Was there already an index?]
Exception caught while booting Guile.
/usr/bin/gdb.minimal: warning: Could not complete Guile gdb module initialization from:
/usr/share/gdb/guile/gdb/boot.scm.
Limited Guile support is available.
Suggest passing --data-directory=/path/to/gdb/data-directory.
Error in function "open-file":
No such file or directory: "/usr/share/gdb/guile/gdb/boot.scm"Error in function "open-file":
No such file or directory: "/usr/share/gdb/guile/gdb/boot.scm"Exception caught while booting Guile.
/usr/bin/gdb.minimal: warning: Could not complete Guile gdb module initialization from:
/usr/share/gdb/guile/gdb/boot.scm.
Limited Guile support is available.
Suggest passing --data-directory=/path/to/gdb/data-directory.
Exception caught while booting Guile.
/usr/bin/gdb.minimal: warning: Could not complete Guile gdb module initialization from:
/usr/share/gdb/guile/gdb/boot.scm.
Limited Guile support is available.
Suggest passing --data-directory=/path/to/gdb/data-directory.
Error in function "open-file":
No such file or directory: "/usr/share/gdb/guile/gdb/boot.scm"Error in function "open-file":
No such file or directory: "/usr/share/gdb/guile/gdb/boot.scm"Error in function "open-file":
No such file or directory: "/usr/share/gdb/guile/gdb/boot.scm"Error in function "open-file":


https://kojipkgs.fedoraproject.org//work/tasks/6549/42216549/build.log

it's a bug in shebang, please ignore this report!

(In reply to Sergio Durigan Junior from comment #6)
> Thanks for the report.  I've pushed a new GDB that fixes this, both on
> Rawhide and F32.

The Fedora 32 build went into the trashcan: https://koji.fedoraproject.org/koji/buildinfo?buildID=1472956

Any plan to backport this to other branches?

(In reply to Simone Caronni from comment #9)

> The Fedora 32 build went into the trashcan:
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1472956

I tried to get it out of the trashcan so that it could be released, but apparently this is not possible.

There is another build problem (in bfd) that needs to be fixed for F32; once that goes in, changes made for gdb-9.1-4.fc32 will go in too.

> Any plan to backport this to other branches?

No, unless there's a really compelling reason to do so.

FEDORA-2020-0bc8abfe7d has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-0bc8abfe7d

FEDORA-2020-0bc8abfe7d has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-0bc8abfe7d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-0bc8abfe7d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2020-0bc8abfe7d has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.