[Mesa-dev] [Bug 36242] New: building with --enable-32-bit on a 64 bit machine fails

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=36242

           Summary: building with --enable-32-bit on a 64 bit machine
                    fails
           Product: Mesa
           Version: git
          Platform: x86-64 (AMD64)
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: medium
         Component: Mesa core
        AssignedTo: mesa-dev at lists.freedesktop.org
        ReportedBy: alexandre.f.demers at gmail.com


It seems building llvmpipe with --enable-32-bit on a 64 bit machine fails.

Looking more closely at the output, the real problem seems to be that some
parts of the code correctly find the /usr/lib32 folder, while others only look
under /usr/lib. And I would also say that the steps looking only under /usr/lib
are related to llvm and , located under /usr/lib/llvm-2.8... In fact, using the
parameter --disable-gallium-llvm fixes a part of the problem, but prevents
building llvmpipe (obviously).

It seems vmwgfx also suffers from a similar problem, looking under /usr/lib for
the libkms, which of course is compiled for 64bit. I'm not even sure there is a
32bit version somewhere on the machine or if it should be... Is there a way or
a parameter to disable building that driver?

I'm calling autogen.sh the following way:
./autogen.sh --prefix=/usr --enable-selinux --enable-gles1 --enable-gles2
--enable-openvg --enable-gl-osmesa --enable-shared-glapi --enable-xcb
--enable-glx-tls --enable-gl-osmesa --with-dri-drivers= --enable-gallium-egl
--disable-gallium-llvm --enable-gallium-svga --disable-gallium-i915
--disable-gallium-i965 --disable-gallium-radeon --enable-gallium-r600
--disable-gallium-nouveau --enable-gallium-swrast
--with-state-trackers=d3d1x,dri,egl,glx,vega,xorg --enable-32-bit
--libdir=/usr/lib32

By the way, I'm using Ubuntu 10.10 64 bit.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.