Bug 61750 - Undefined references linking libGLESv2 when configured with --disable-dri
Summary: Undefined references linking libGLESv2 when configured with --disable-dri
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-03 19:05 UTC by Wladimir
Modified: 2019-09-18 20:23 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Wladimir 2013-03-03 19:05:24 UTC 
Looks like in this case the dispatch library doesn't get built, and also not linked against:

../mesa/lib/libGLESv2.so: undefined reference to `_glapi_Dispatch'
../mesa/lib/libGLESv2.so: undefined reference to `_glapi_get_dispatch'

Enabling dri, but disabling all the drivers with --gallium-drivers= solved the isssue.

Mesa git commit: 0b6e72f
Comment 1 Matt Turner 2013-03-03 20:28:00 UTC 
Thanks for the reminder. Disallowing GLES + non-DRI has been on my todo list.

Is there a reason GLES + non-DRI is useful?
Comment 2 Wladimir 2013-03-03 20:36:36 UTC 
I'm not sure. I was trying to compile mesa+gallium with as few dependencies as possible (no X11, no external drivers, only soft pipe) and DRI was requesting some Radeon library so I completely disabled it.

It was later told me that it is possible to build with DRI but without drivers. This works fine, really, and I do not have any reason to still want it the other way.

If the requested scenario is useless or unsupported, it would be nice if configure gave a warning.
Comment 3 Jakob Bornecrantz 2013-03-04 01:42:10 UTC 
Well currently libGL isn't built at all if you pass --disable-[glx|dri] so you would not get anything working then if you did that.

Also considering GLES is available on more platforms then DRI (even linux based) I can see the usefulness of a software rasterizer being buildable there.

Cheers, Jakob.
Comment 4 Will Wagner 2014-04-07 15:50:17 UTC 
This appears to be a duplicate of bug 75098?
Comment 5 GitLab Migration User 2019-09-18 20:23:08 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/975.

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.