Bug 152253 – [jhbuild] Fails to build Mesa

• Component: WebKitGTK
• Status: RESOLVED WONTFIX

[Sergio Villar Senin]

Mesa fails to build against llvm.

make[3]: Entering directory '/opt/WebKit/WebKitBuild/DependenciesGTK/Build/Mesa/src/gallium/targets/libgl-xlib'
  CXXLD    libGL.la
../../../../src/gallium/auxiliary/.libs/libgallium.a(lp_bld_misc.o): In function `llvm::RTDyldMemoryManager::getSymbolAddress(std::string const&)':
/opt/WebKit/WebKitBuild/DependenciesGTK/Root/include/llvm/ExecutionEngine/RTDyldMemoryManager.h:73: undefined reference to `llvm::RTDyldMemoryManager::getSymbolAddressInProcess(std::string const&)'
/opt/WebKit/WebKitBuild/DependenciesGTK/Root/include/llvm/ExecutionEngine/RTDyldMemoryManager.h:73: undefined reference to `llvm::RTDyldMemoryManager::getSymbolAddressInProcess(std::string const&)'
collect2: error: ld returned 1 exit status
Makefile:639: recipe for target 'libGL.la' failed
make[3]: *** [libGL.la] Error 1

[Sergio Villar Senin]

I've just checked that 10.5.4 (the one we're using before r193618) links that particular file perfectly (although it fails later due to some other functions).

[Sergio Villar Senin]

Looks like the problem was introduced in mesa 10.6.8. The problem is that we cannot use 10.6.7 due to our too modern LLVM

[Carlos Alberto Lopez Perez]

(In reply to comment #2)
> Looks like the problem was introduced in mesa 10.6.8. The problem is that we
> cannot use 10.6.7 due to our too modern LLVM

Michael updated Mesa to 11.0.6 in r193618 <http://trac.webkit.org/r193618> 

Why you are trying to build 10.6.x?

[Sergio Villar Senin]

(In reply to comment #3)
> (In reply to comment #2)
> > Looks like the problem was introduced in mesa 10.6.8. The problem is that we
> > cannot use 10.6.7 due to our too modern LLVM
> 
> Michael updated Mesa to 11.0.6 in r193618 <http://trac.webkit.org/r193618> 
> 
> Why you are trying to build 10.6.x?

I tried with different mesa/llvm combinations to check when the problem started.

It turns out that the current combination of llvm/mesa only builds with gcc-5, so the jhbuild is broken for gcc 4.x.

[Carlos Alberto Lopez Perez]

(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #2)
> > > Looks like the problem was introduced in mesa 10.6.8. The problem is that we
> > > cannot use 10.6.7 due to our too modern LLVM
> > 
> > Michael updated Mesa to 11.0.6 in r193618 <http://trac.webkit.org/r193618> 
> > 
> > Why you are trying to build 10.6.x?
> 
> I tried with different mesa/llvm combinations to check when the problem
> started.
> 
> It turns out that the current combination of llvm/mesa only builds with
> gcc-5, so the jhbuild is broken for gcc 4.x.

The bots are running gcc 4.9, and it is building fine there...

I think it should be something else.

Can you check on the configure step of mesa if it is picking the llvm from the jhbuild? Otherwise can you try to pass the option "--with-llvm-prefix=$YOURWEBKITBUILDIR/WebKitBuild/DependenciesGTK/Root" ?

[Carlos Alberto Lopez Perez]

This is how the configure step looks on the bots:


        prefix:          /home/slave/webkitgtk/gtk-linux-64-release/build/WebKitBuild/DependenciesGTK/Root
        exec_prefix:     ${prefix}
        libdir:          ${exec_prefix}/lib
        includedir:      ${prefix}/include

        OpenGL:          yes (ES1: yes ES2: yes)

        OSMesa:          no

        GLX:             Xlib-based

        EGL:             no

        llvm:            yes
        llvm-config:     /home/slave/webkitgtk/gtk-linux-64-release/build/WebKitBuild/DependenciesGTK/Root/bin/llvm-config
        llvm-version:    3.7.0

        Gallium:         yes

        Shared libs:     yes
        Static libs:     no
        Shared-glapi:    yes

        CFLAGS:          -pipe -Wall -std=c99 -Werror=implicit-function-declaration -Werror=missing-prototypes -fno-strict-aliasing -fno-math-errno -fno-trapping-math -fno-builtin-memcmp
        CXXFLAGS:        -pipe -Wall -fno-strict-aliasing -fno-builtin-memcmp
        Macros:          -D__STDC_LIMIT_MACROS -D_GNU_SOURCE -DUSE_SSE41 -DNDEBUG -DUSE_X86_64_ASM -DHAVE_XLOCALE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STRTOF -DHAVE_MKOSTEMP -DHAVE_DLOPEN -DHAVE_POSIX_MEMALIGN -DUSE_XSHM -DMESA_EGL_NO_X11_HEADERS -DHAVE_LLVM=0x0307 -DMESA_LLVM_VERSION_PATCH=0

        LLVM_CFLAGS:     -I/home/slave/webkitgtk/gtk-linux-64-release/build/WebKitBuild/DependenciesGTK/Root/include   -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
        LLVM_CXXFLAGS:   -I/home/slave/webkitgtk/gtk-linux-64-release/build/WebKitBuild/DependenciesGTK/Root/include   -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS   -std=c++11   -fno-rtti    
        LLVM_CPPFLAGS:   -I/home/slave/webkitgtk/gtk-linux-64-release/build/WebKitBuild/DependenciesGTK/Root/include   -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
        LLVM_LDFLAGS:    -L/home/slave/webkitgtk/gtk-linux-64-release/build/WebKitBuild/DependenciesGTK/Root/lib 

        PYTHON2:         python2



From: https://build.webkit.org/builders/GTK%20Linux%2064-bit%20Release%20%28Build%29/builds/64803/steps/jhbuild/logs/stdio

[Sergio Villar Senin]

(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #3)
> > > (In reply to comment #2)
> > > > Looks like the problem was introduced in mesa 10.6.8. The problem is that we
> > > > cannot use 10.6.7 due to our too modern LLVM
> > > 
> > > Michael updated Mesa to 11.0.6 in r193618 <http://trac.webkit.org/r193618> 
> > > 
> > > Why you are trying to build 10.6.x?
> > 
> > I tried with different mesa/llvm combinations to check when the problem
> > started.
> > 
> > It turns out that the current combination of llvm/mesa only builds with
> > gcc-5, so the jhbuild is broken for gcc 4.x.
> 
> The bots are running gcc 4.9, and it is building fine there...
> 
> I think it should be something else.

Well I don't know. The fact is that using gcc-5 allowed me to finish the build.

[Sergio Villar Senin]

I don't think gcc 4.x is supported anymore.