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.

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

libffi-3.3 x86_64-pc-linux-gnu build error with Clang + LTO #626

Open
telans opened this issue Mar 6, 2021 · 3 comments
Open

libffi-3.3 x86_64-pc-linux-gnu build error with Clang + LTO #626

telans opened this issue Mar 6, 2021 · 3 comments

Comments

@telans
Copy link

telans commented Mar 6, 2021

System Details

Gentoo x86_64-pc-linux-gnu

clang version 12.0.0
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/lib/llvm/12/bin
Selected GCC installation: /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Selected multilib: .;@m64
CFLAGS='-march=znver2 -O3 -flto=thin -pipe'
CXXFLAGS='-march=znver2 -O3 -flto=thin -pipe'

Problems Description

Build failure when compiling:
error: changed section flags for .eh_frame, expected: 0x2

There are no issues when comping with Clang & no LTO, nor when compiling with GCC + LTO

libtool: compile:  clang -m32 -DHAVE_CONFIG_H -I. -I/var/tmp/portage/dev-libs/libffi-3.3-r2/work/libffi-3.3 -I. -I/var/tmp/portage/dev-libs/libffi-3.3-r2/work/libffi-3.3/include -Iinclude -I/var/tmp/portage/dev-libs/libffi-3.3-r2/work/libffi-3.3/src -I. -I/var/tmp/portage/dev-libs/libffi-3.3-r2/work/libffi-3.3/include -Iinclude -I/var/tmp/portage/dev-libs/libffi-3.3-r2/work/libffi-3.3/src -march=znver2 -O3 -flto -pipe -c /var/tmp/portage/dev-libs/libffi-3.3-r2/work/libffi-3.3/src/x86/sysv.S  -fPIC -DPIC -o src/x86/.libs/sysv.o
/var/tmp/portage/dev-libs/libffi-3.3-r2/work/libffi-3.3/src/x86/sysv.S:832:1: error: changed section flags for .eh_frame, expected: 0x2
.section .eh_frame,"aw",@progbits
^
make[2]: *** [Makefile:1254: src/x86/sysv.lo] Error 1
@TheK0tYaRa
Copy link

The issue persists with -O2 and on package version 3.3-r2

@mhsmith
Copy link

mhsmith commented Nov 21, 2023

This looks like a duplicate of #638, which has now been fixed.

@TheK0tYaRa
Copy link

I don't think that's how time works, but alright.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants