Skip to content

Failed to start tiglviewer-3 due to MESA_GLSL_CACHE_DISABLE #1069

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
BeccyB opened this issue Mar 11, 2025 · 3 comments · May be fixed by #1074
Open

Failed to start tiglviewer-3 due to MESA_GLSL_CACHE_DISABLE #1069

BeccyB opened this issue Mar 11, 2025 · 3 comments · May be fixed by #1074

Comments

@BeccyB
Copy link

BeccyB commented Mar 11, 2025

After building on linux with

cmake .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=install -DOCE_STATIC_LIBS=ON -DTIGL_BUILD_TESTS=ON -DCMAKE_CXX_FLAGS=-fno-stack-protector

I get the following error:

*** MESA_GLSL_CACHE_DISABLE is deprecated; use MESA_SHADER_CACHE_DISABLE instead ***
*** stack smashing detected ***: terminated
Aborted

After adding the flag -DTIGL_BUILD_TESTS=ON -DCMAKE_CXX_FLAGS=-fno-stack-protector I now see a short 1 sec glimps of a gui before crashing.

@BeccyB
Copy link
Author

BeccyB commented Mar 11, 2025

This is the python env that I am using tigl_conda.txt

@BeccyB
Copy link
Author

BeccyB commented Mar 11, 2025

The problem seems to be the python env. It works with this older version:

tigl_conda.txt

@svengoldberg
Copy link
Contributor

This problem results from naming conflicts. The newer conda environment installs its own GL (because of a newer QT). The used system already has GL installed. Therefore, we use the old QT version. That should fix this issue.

svengoldberg added a commit that referenced this issue Apr 8, 2025
With the (current) QT version 5.15.8 used in the conda environment, a naming conflict appears since there are two libraries with the same name. One comes with conda and the other one is already installed within the system. The problem is related to OpenGL (GL, GLX) and results in CMake not being able to find the correct runtime path as it was ambiguous. At the end, the TiGLViewer was not executable due to that. We found out that an explicit linking against OpenGL is not necessary (anymore ?) since it already comes with OCCT. Hence, we deactivated the linking which also solved this issue (#1069).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants