Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RPMLint on openSUSE thumbleweed does not like liblcf #9

Open
carstene1ns opened this issue Apr 27, 2020 · 2 comments
Open

RPMLint on openSUSE thumbleweed does not like liblcf #9

carstene1ns opened this issue Apr 27, 2020 · 2 comments

Comments

@carstene1ns
Copy link
Member

LTO is enabled by default on SUSE Tumbleweed. Seems we have fat lto objects... 🐐

[   59s] RPMLINT report:
[   59s] ===============
[   60s] liblcf0-devel.i586: E: lto-no-text-in-archive (Badness: 10000) /usr/lib/liblcf.a
[   60s] This archive does not contain a non-empty .text section.  The archive was not
[   60s] created with -ffat-lto-objects option.

Possible solution:
zeromq/libzmq@3e4c90b
@Ghabry
Copy link
Member

Ghabry commented Apr 27, 2020

CMake has INTERPROCEDURAL_OPTIMIZATION but this sets -flto -fno-fat-lto-objects so the opposite of what Suse wants :/

@Ghabry
Copy link
Member

Ghabry commented Apr 27, 2020

CMake workaround. The behaviour of fat-lto-objects can't be directly configured from the CMake command line, is hardcoded: https://gitlab.kitware.com/cmake/cmake/issues/16808

carstene1ns added a commit that referenced this issue Apr 28, 2020
@carstene1ns
liblcf: Fixes for Fedora and SUSE
c073a3f 
Force LTO flag, see #9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Ghabry @carstene1ns