| Summary: | glsl compiler builds OK for x86_64, NOT for i686 | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Jason Vas Dias <jason.vas.dias> |
| Component: | glsl-compiler | Assignee: | Ian Romanick <idr> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Jason Vas Dias
2011-04-21 08:45:37 UTC
actually, no, it can't be a missing i686 version of python module, else python would complain. Do I need to be running a 32-bit version of python for this to work ? Aha! sorry - nothing to do with python - $ ./builtin_compiler Segmentation fault am investigating ... Ach! sorry, it was a bad libgcc_s.so.1 link. fixed now. Maybe use -static-libgcc for builtin_compiler ? sorry for this bug, but I also meant to ask - do those config options look alright ? Any suggestions for improving them ? not really a GL expert here. And do I really need libEGL.so for best GL performance on a radeonhd ? There was so much about EGL in the docs and config, I went and found some libEGL.so source on the web and built it - but is it really required for my platform ? Any advice would be most appreciated, thanks. Aha! I needed to add : --enable-openvg --enable-gallium-nouveau to configure args. But please, can anyone tell me - is this really needed / required for best GL / 3d performance on radeonhd : radeon X1250 : 01:05.0 VGA compatible controller: ATI Technologies Inc RS690M [Radeon X1200 Series] (prog-if 00 [VGA controller]) And I needed to do: ../../drm/configure --prefix=/usr --libdir=/usr/lib64 --enable-shared --with-pic --disable-intel --enable-radeon --enable-nouveau-experimental-api --with-kernel-source=/usr/src/linux But is this --enable-nouveau-experimental-api required / recommended for radeonhd ? Everything with "nouveau" in the name is just for the driver for NVIDIA chips. These shouldn't make any difference whatsoever for the Radeon drivers. libEGL is only needed if you have applications that use the EGL API. (In reply to comment #7) > Everything with "nouveau" in the name is just for the driver for NVIDIA chips. > These shouldn't make any difference whatsoever for the Radeon drivers. > > libEGL is only needed if you have applications that use the EGL API. Thanks Ian - but libdrm does not ship at least one required header : 'nouveau_pushbuf.h' if I build libdrm without '--enable-nouveau-experimental-api - this header is required when mesa/mesa is built with : --enable-gles2 \ --enable-openvg --enable-gallium-nouveau \ which I understood to be the 'recommended way to enable libEGL' from : http://mesa3d.sourceforge.net/ : "Build EGL Run configure with the desired client APIs and enable the driver for your hardware. For example: $ ./configure --enable-gles2 --enable-openvg --enable-gallium-nouveau " Aha ! $ mesa/mesa/configure --help 2>&1 | grep gallium --enable-gallium-radeon build gallium radeon [default=disabled] --enable-gallium-r600 build gallium radeon [default=disabled] --disable-gallium build gallium [default=enabled] --enable-gallium-egl enable gallium EGL state tracker [default=auto] --enable-gallium-llvm build gallium LLVM support [default=disabled] --enable-gallium-svga build gallium SVGA [default=disabled] --enable-gallium-i915 build gallium i915 [default=disabled] --enable-gallium-i965 build gallium i965 [default=disabled] --enable-gallium-radeon build gallium radeon [default=disabled] --enable-gallium-r600 build gallium radeon [default=disabled] --enable-gallium-nouveau build gallium nouveau [default=disabled] --enable-gallium-swrast build gallium swrast [default=auto] I guess I should rebuild with '--enable-gallium-radeon --enable-gallium-r600' . Oops. But my question above was is "--enable-gallium-*" / libEGL really required to get best graphics performance out of: 01:05.0 VGA compatible controller: ATI Technologies Inc RS690M [Radeon X1200 Series] ? |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.