Bug 55919

The next error is:
../../../../src/gallium/drivers/nouveau/nouveau_winsys.h:7:32: fatal error: nouveau/nouveau_bo.h: No such file or directory

I found out that although I have problems with the drivers I could build
./lib/libOpenVG.so.1.0.0
./lib/libOpenVG.so.1
./lib/libOpenVG.so
./lib/libGL.so.1.5.071100
./lib/libGL.so.1
./lib/libGL.so
./lib/libOSMesa.so.7.11.0
./lib/libOSMesa.so.7
./lib/libOSMesa.so

with make linux -k

And 
make linux-osmesa
build
/lib/libOSMesa.so.7.11.0
./lib/libOSMesa.so.7
./lib/libOSMesa.so
./lib/libGLU.so.1.3.071100
./lib/libGLU.so.1
./lib/libGLU.so

So libGLU is only compiled if I use make linux-osmesa. Is that correct?
I had to remove the -ansi compiler flag because otherwise it has problems 
with c++ comments //

Do you have only problems with version 7.11 ? Have you tried 9.0 ?

It's an old version of mesa so you need an old version of libdrm if you want to build nouveau, 2.4.33 or earlier in this case. You can also keep the headers and libdrm_nouveau.so of both old and new versions installed if you want.

But if you don't want to build nouveau anyway, disable/don't enable it with the configure script (--with-gallium-drivers=...). It shouldn't even be selected by default.

Hi,
thank you. Running configure fails, so I just ran 
make linux
after little manually configurating the file in the configs directory.
I'll try to find the old libdrm and will try to use it.

I fetched libdrm-2.4.24

and after configure I got:
libdrm 2.4.24 will be compiled with:

  libkms         yes
  Intel API      yes
  vmwgfx API     no
  Radeon API     yes
  Nouveau API    no

Therefor I tried configure with --enable-nouveau-experimental-api

The goog thing is that the important libraries are build before it tries to build these strange driver that needs nouveau. There should be a possibility to disable nouveau in the config files, too. That would be very nice especially after the nouveau thing is experimental.

After building and installing the lib I added the LD_LIBRARY_PATH to the install directory for libdrm and added the include path to the configs/linux file.
Let's see if that helps ;)

Now the build succeeds and I got libEGL.so and libGLw.so as additional libraries. Which one contains the nouveau driver and what are the advantages of having libEGL.so and libGLw.so?

I tested configure and had to install
glproto-1.4.16, dri2proto-2.8 and libdrm-2.4.24 and set the PKG_CONFIG_PATH

Afterwards configure fails with
checking for llvm-config... no
configure: error: LLVM is required to build Gallium R300 on x86 and x86_64

There is a nice configure option
  --enable-gallium-llvm   build gallium LLVM support [default=enabled on
                          x86/x86_64]
Is it possible to disable that option? Trying 
--disable-gallium-llvm does not help

I succeeded with the configure optio
--with-gallium-drivers=""
and recieved
        prefix:          /tmp/Mesa
        exec_prefix:     ${prefix}
        libdir:          ${exec_prefix}/lib
        includedir:      ${prefix}/include

        OpenGL:          yes (ES1: no ES2: no)
        OpenVG:          no

        Driver:          dri
        OSMesa:          no
        DRI drivers:     i915 i965 mach64 mga nouveau r128 r200 r300 r600 radeon savage tdfx unichrome swrast
        DRI driver dir:  ${libdir}/dri
        Use XCB:         no
        Shared dricore:  no

        GLU:             yes
        GLw:             yes (Motif: no)
        glut:            no

        EGL:             yes
        EGL platforms:   x11
        EGL drivers:     builtin:egl_glx

        llvm:            no

        Gallium:         no

        Shared libs:     yes
        Static libs:     no

        CFLAGS:          -g -O2 -Wall -Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -fPIC
        CXXFLAGS:        -g -O2 -Wall -fno-strict-aliasing -fPIC
        Macros:          -D_GNU_SOURCE -DPTHREADS -DHAVE_POSIX_MEMALIGN -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING -DGLX_INDIRECT_RENDERING -DHAVE_ALIAS -DUSE_X86_64_ASM

        PYTHON2:         python2

        Run 'gmake' to build Mesa

After successful configure I got:
glxconfig.c:52:11: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘int’
glxconfig.c:223:11: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘struct’
glxconfig.c:266:11: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘void’
glxconfig.c:287:11: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘struct’
glxconfig.c:299:11: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘struct’
gmake[2]: *** [glxconfig.o] Error 1
gmake[2]: *** Waiting for unfinished jobs....
glxext.c:65:11: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘int’
glxext.c:351:11: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘void’
glxext.c:709:11: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘int’
glxext.c:725:11: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘void’
...
At this point the following shared libs are build:
./src/mesa/drivers/dri/i915/i915_dri.so
./src/mesa/drivers/dri/i965/i965_dri.so
./src/mesa/drivers/dri/mach64/mach64_dri.so
./src/mesa/drivers/dri/mga/mga_dri.so
./src/mesa/drivers/dri/nouveau/nouveau_vieux_dri.so
./src/mesa/drivers/dri/r128/r128_dri.so
./src/mesa/drivers/dri/r200/r200_dri.so
./src/mesa/drivers/dri/r300/r300_dri.so
./src/mesa/drivers/dri/r600/r600_dri.so
./src/mesa/drivers/dri/radeon/radeon_dri.so
./src/mesa/drivers/dri/savage/savage_dri.so
./src/mesa/drivers/dri/swrast/swrast_dri.so
./src/mesa/drivers/dri/tdfx/tdfx_dri.so
./src/mesa/drivers/dri/unichrome/unichrome_dri.so
./lib/i915_dri.so
./lib/i965_dri.so
./lib/mach64_dri.so
./lib/mga_dri.so
./lib/nouveau_vieux_dri.so
./lib/r128_dri.so
./lib/r200_dri.so
./lib/r300_dri.so
./lib/r600_dri.so
./lib/radeon_dri.so
./lib/savage_dri.so
./lib/tdfx_dri.so
./lib/unichrome_dri.so
./lib/swrast_dri.so

That's bad because all GL libs are not build so far. Thank god the build/compile process works with the old config and without the configure.

Why is it marked as resolved invalid?
Regards,
  Roland