Summary: | 12.0.0-rc3: mesa_dri_drivers.so linking fails with: relocation R_X86_64_32S against `V4F_COUNT' can not be used when making a shared object | ||
---|---|---|---|
Product: | Mesa | Reporter: | warpme |
Component: | Mesa core | Assignee: | mesa-dev |
Status: | RESOLVED INVALID | QA Contact: | mesa-dev |
Severity: | normal | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
warpme
2016-06-16 09:17:31 UTC
FYI: ppl from Phoronix forums located the cause of the problem: gen_matypes.c is passed to the compiler in order to generate assembly code in text form (compiler switch: -S), but with -flto GCC doesn't output any code nor data because that is postponed to link time. In such case gcc -S -flto generates a file with empty .text and .data sections. This isn't a GCC bug. Passing -ffat-lto-objects solves issue for me so maybe if compile passes -S together with -flto then the config should imply -ffat-lto-objects ? The using the link time optimisation flag is not an officially supported way to build mesa. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.