Bug 1193198

Summary: Mesa build error with GCC 5
Product: [Fedora] Fedora Reporter: Vinson Lee <vlee>
Component: gccAssignee: Jakub Jelinek <jakub>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: davejohansen, jakub, law
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-16 20:44:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vinson Lee 2015-02-16 20:37:02 UTC
Description of problem:
Mesa does not build with GCC 5.


Version-Release number of selected component (if applicable):
gcc-5.0.0-0.13.fc23.x86_64


How reproducible:
100%


Steps to Reproduce:
1. make
2.
3.

Actual results:
  CXXLD    gallium_drv_video.la
../../../../src/gallium/auxiliary/.libs/libgallium.a(lp_bld_misc.o):(.data.rel.ro._ZTV26DelegatingJITMemoryManager[_ZTV26DelegatingJITMemoryManager]+0x50): undefined reference to `llvm::RTDyldMemoryManager::getSymbolAddress(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
../../../../src/gallium/auxiliary/.libs/libgallium.a(lp_bld_misc.o):(.data.rel.ro._ZTV19ShaderMemoryManager[_ZTV19ShaderMemoryManager]+0x50): undefined reference to `llvm::RTDyldMemoryManager::getSymbolAddress(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'


Expected results:


Additional info:
Mesa builds on Fedora 21 with GCC 4.9.

Comment 1 Jakub Jelinek 2015-02-16 20:44:27 UTC
Please read http://developerblog.redhat.com/2015/02/05/gcc5-and-the-c11-abi/
and http://developerblog.redhat.com/2015/02/10/gcc-5-in-fedora/ and
In short, in F23 there is C++ ABI change and everything needs to be rebuilt, in topological order.  So, in this case you need to rebuild llvm first.