Nguyen Vu Hung wrote:
2010/10/2 Jesús Corrius <jesus@softcatala.org>
[vuhung@www2 slideshow]$ rpm -qf /usr/include/GL/glxext.h
mesa-libGL-devel-6.5.1-7.8.el5
This is the standard rpm on CentOS 5.5 that I has installed with yum
in
st
al
This mesa version is more than 4 years old and the problem may be
related to that.
I assume that CentOS 5.5 is technically indentical to Redhat 5.5. So
Question: Does anyone gets the similar problem on Redhat?
Looks like the following ifdef:
#if defined( GLX_VERSION_1_3 ) && defined( GLX_EXT_texture_from_pixmap )
doesn't work well with your version of the mesa package. The program
will probably compile if you undefine one of the constants above, but
I am unsure about the side effects.
Ignore the side effects we may encounter,
I haved a line
#undef GLX_VERSION_1_3 to the top of the following file
source/engine/OGLTrans/OGLTrans_TransitionerImpl.cxx:#if defined(
GLX_VERSION_1_3 ) && defined( GLX_EXT_texture_from_pixmap )
then re configure and make.
Everything seems fine now.
Thanks for hunting this down - could you extract a proper patch from
your sources, so we can fix this once and for all?
Let's keep development/code-related discussions on the libreoffice
list. :)
Cheers,
-- Thorsten
--
To unsubscribe, send an empty e-mail to discuss+unsubscribe@documentfoundation.org
All messages you send to this list will be publicly archived and cannot be deleted.
List archives are available at http://www.documentfoundation.org/lists/discuss/
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.