Bug 61200 - insufficient linking of libxatracker.so
Summary: insufficient linking of libxatracker.so
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Other (show other bugs)
Version: git
Hardware: All All
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-21 02:45 UTC by Rafał Mużyło
Modified: 2013-02-22 09:40 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
possible fix (988 bytes, patch)
2013-02-21 09:01 UTC, Andreas Boll
Details | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Rafał Mużyło 2013-02-21 02:45:12 UTC
See https://bugs.gentoo.org/show_bug.cgi?id=458300 for the problem and possible solution (similar to the one used for OSMesa).

On not quite related note: it would seem constructs like 'AC_ARG_ENABLE([xlib_glx],' aren't quite correct - to match AS_HELP_STRING, they should be 'AC_ARG_ENABLE([xlib-glx],', cause while the corect var to check for will have an underscore, '--enable-FEATURE' string takes FEATURE from first argument of the macro.
Comment 1 Andreas Boll 2013-02-21 09:01:54 UTC
Created attachment 75240 [details] [review]
possible fix

Does this patch help?
Comment 2 Rafał Mużyło 2013-02-21 12:56:03 UTC
(In reply to comment #1)
> Created attachment 75240 [details] [review] [review]
> possible fix
> 
> Does this patch help?

Well, it should help - that's exactly the solution I've proposed.
On the other hand, I'm not the original reporter - I've only moved it here, so that 9.1 gets the fix before its release.

The downstream bug has been just been updated - will get back to you.
Comment 3 Andreas Boll 2013-02-22 09:40:21 UTC
Fixed by commit c1eb585f3d62670782d9cc73637b7e3bcab46d66
Cherry-picked to the 9.1 branch: be7048477a2989bd11ab590c65ea1515f764a86c

It will be available in Mesa 9.1

Please reopen the bug if the problem still exists.


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.