Hello,
I have been trying to build Avogadrolibs
https://github.com/OpenChemistry/avogadrolibs https://build.opensuse.org/package/live_build_log/home:andythe_great/avogadr...
However, this error prevent it from building. E: lto-no-text-in-archive (Badness: 10000)
I found this documentation:
https://en.opensuse.org/openSUSE:LTO#LTO_enablement_in_openSUSE:Factory Which it says to add the flag %global _lto_cflags %{?_lto_cflags} -ffat-lto-objects to fix the issue which it did.
But Science repo maintainer won't accept it as a fix. https://build.opensuse.org/request/show/780593 But it is correct solution to rpmlint error
So I ask in openSUSE forum, which was told that it got something to do with reproducibility. https://forums.opensuse.org/showthread.php/539911-How-to-detect-GCC-using-CM...) Not related to reproducibility at all
I decide to ask the Avogadro dev to fix the issue but neither me, openSUSE forum admin or Avogadro dev understand why should it be done. https://github.com/OpenChemistry/avogadrolibs/issues/455
Which the issue remain unsolved, so I would like to know what E: lto- no-text-in-archive means so I can tell the Avogadro dev why they should fix it and why it is exclusive to openSUSE. Afaik it is not something upstream should be fixing - for static
Hi On Sat, 2020-05-02 at 04:42 +0000, andythe_great wrote: libaries extra build flag has to be used, so that static librarr contains both binary and lto bytecode - rpmlint says that you have just bytecode. I suggest you reopen sr#780593 Cheers Martin -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org