https://bugs.freedesktop.org/show_bug.cgi?id=80848
--- Comment #20 from Emil Velikov <emil.l.veli...@gmail.com> --- (In reply to comment #19) > (In reply to comment #18) > > I had cross-compilation problems on Ubuntu (building 32bit Mesa on 64bit > > environment) and my problems went away by reverting > > > > 3ecd9e1a93817180fa5b280e5fe11c903cca38ba > > > > For some reason otherwise a wrong version (64bit one) of libexpat got > > included to linking. Patch adds $(EXPAT_LIBS) when linking libloader so that > > is why I tried the revert. I'll try to see why this happens. > > whoopsie forgot to paste my build command line: > > INTEL_CFLAGS='-I/opt/include -I/opt/include/libdrm' INTEL_LIBS='-L/opt/lib > -ldrm_intel' CFLAGS='-m32' CXXFLAGS='-m32' ./autogen.sh --prefix=/opt > --enable-gles2 --without-gallium-drivers --enable-32-bit > --with-dri-drivers=i965 --with-egl-platforms=x11 --disable-osmesa > --disable-vdpau --disable-dri3 --enable-debug --enable-glx-tls > --enable-texture-float I find something a bit disturbing here - why would you set INTEL_{CFLAGS,LIBS} rather than relying on pkg-config ? Your native arch is x86-64 thus the lack of PKG_CONFIG_PATH is the one causing you problems - pkgconfig looks for the variable (none set) then goes into the default dir which has a .pc file pointing to a 64bit library. Or to put things in a different light - please can we avoid shooting mesa in the back by providing any other flags but PKG_CONFIG_PATH, CFLAGS and CXXFLAGS. Thank you P.S. Things should just work even without C{XX,}FLAGS='-m32' unless we have a bug somewhere :) -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev