** Changed in: mesa
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1066599
Title:
Wine is unable to detect OSMesa correctly when compiling from s
This bug was fixed in the package mesa - 9.1.4-0ubuntu3
---
mesa (9.1.4-0ubuntu3) saucy; urgency=low
* Add fix-os-mesa-exports.diff from upstream. (LP: #1066599)
-- Maarten LankhorstTue, 16 Jul 2013
11:29:32 +0200
** Changed in: mesa (Ubuntu)
Status: Confirmed => Fix R
** Branch linked: lp:ubuntu/saucy-proposed/mesa
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1066599
Title:
Wine is unable to detect OSMesa correctly when compiling from source
Status
I posted a patch on the upstream bug, which should make osmesa work
correctly again with shared glapi, without building twice.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1066599
Title:
Created attachment 82036
fix?
I have no idea how much this helps, but give it a shot..
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1066599
Title:
Wine is unable to detect OSMesa corr
Created attachment 44820
configure patched
I had to patch configure a little to make OSMesa be detectable, see
attached file.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1066599
Title:
(In reply to comment #11)
> Therefore, distributions need to build libOSMesa separately, which is not been
> done in Arch, Debian, Ubuntu currently.
>
> Is this the right way to compile Mesa? Is there any distributions already do
> things right?
On Mageia we build Mesa twice (first the rest with
>From my experience on Saucy, it doesn't matter whether proprietary
driver is enabled or not.
The message is just a warning at the end of configure, not a stopper.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://b
Am I right that if you never have proprietary libgl on your system then
Wine builds properly?
That would explain why the build daemons seem to get it right but this
problem hits users desktops.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribe
Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=47824.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
** Bug watch added: freedesktop.org Bugzilla #47824
https://bugs.freedesktop.org/show_bug.cgi?id=47824
** Changed in: mesa
Remote watch: freedesktop.org Bugzilla #53179 => freedesktop.org Bugzilla
#47824
--
You received this bug notification because you are a member of Desktop
Packages, whi
Hi,
The upstream Mesa fix won't get distributions' libOSMesa right
automatically.
It seems that libOSMesa need to be compiled without --enable-shared-
glapi while other Mesa components need --enable-shared-glapi
Therefore, distributions need to build libOSMesa separately, which is
not been done
The upstream fix basically make it _possible_ to compile OSMesa without
shared glapi.
It seems that Mesa components except OSMesa do need --enable-shared-
glapi .
So I currently work around this issue as I don't install libosmesa* from
the repository.
Instead, I compile libOSMesa manually as:
#
Still a problem in Saucy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1066599
Title:
Wine is unable to detect OSMesa correctly when compiling from source
Status in Mesa:
Unknown
Sta
The linked os mesa bug says it was fixed in 9.0, and Ubuntu seems to
have a version later than that available (in raring as well), is this
still an issue?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launch
** Tags added: saucy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1066599
Title:
Wine is unable to detect OSMesa correctly when compiling from source
Status in Mesa:
Unknown
Status
** Changed in: mesa (Ubuntu)
Assignee: Ubuntu-X (ubuntu-x-swat) => Canonical X.org (canonical-x)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1066599
Title:
Wine is unable to dete
*** Bug 32974 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1066599
Title:
Wine is unable to detect OSMesa correctly when compiling from
According to a comment in Wine, the issue could be that Mesa is been
build with shared glapi. How can I verify if this is the case?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1066599
T
I have opened a new bug with the Wine team since I have tested with Mesa
9.2 from xorg-edgers and I'm still getting the same error. The link to
the bug is: http://bugs.winehq.org/show_bug.cgi?id=32974
** Bug watch added: Wine Bugzilla #32974
http://bugs.winehq.org/show_bug.cgi?id=32974
--
You
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1066599
T
This is also a problem in Ubuntu 13.04 with packages libosmesa and
libosmesa-dev version 9.0-0ubuntu1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1066599
Title:
Wine is unable to dete
I don't know anything about wine but it looks to me like something might
have changed in the libosmesa6-dev package.
I am using the libosmesa6-dev package on Ubuntu and it seems like the
recent update to 9.0-0ubuntu1 from 8.0.4-0ubuntu0.1 broke my compile.
After the update my project couldn't link
It's also an issue with the package in Xorg-edgers, libosmesa and
libosmesa-dev version 9.1~git20121020.d2b0338e-0ubuntu0ricotz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1066599
Title
Launchpad has imported 10 comments from the remote bug at
http://bugs.winehq.org/show_bug.cgi?id=31904.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.laun
** Also affects: mesa via
https://bugs.freedesktop.org/show_bug.cgi?id=53179
Importance: Unknown
Status: Unknown
** Bug watch added: Wine Bugzilla #31904
http://bugs.winehq.org/show_bug.cgi?id=31904
** Also affects: wine via
http://bugs.winehq.org/show_bug.cgi?id=31904
Impor
I have installed libosmesa6-dev version 9.0-0ubuntu1, I have retested
with the latest git from wine and the problem is still there.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1066599
T
This appears to be a problem with WineHQ and not the packages as
upstream indicates this problem was fixed
https://bugs.freedesktop.org/show_bug.cgi?id=53179. In synaptic can you
verify the version of libosmesa6-dev and also try pulling down the
latest git for WineHQ and trying again.
** Bug watc
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) => Ubuntu-X (ubuntu-x-swat)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1066599
Title:
Wine is unable to detect OSMesa correct
Hi AG, I already have installed libosmesa6 and libosmesa6-dev, and Wine
is unable to find them, that's why i'm filling the bug. The problem with
using the ubuntu-wine packages is that they only provide a package of
the latests release, but I'm trying to compile the daily version to test
the new com
Btw, in the above navigate to https://launchpad.net/~ubuntu-wine
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1066599
Title:
Wine is unable to detect OSMesa correctly when compiling fr
Jamie, you should probably try the following 'https://launchpad.net
/~ubuntu-wine' as they might be able to help you more as this is not
really a graphics or video related issue. It's usually one of those
annoying things about compiling programs from scratch is the "easter egg
hunt" of getting all
I'm attaching the config.log that Wine genereated when compiling from
source.
** Attachment added: "Config.log"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1066599/+attachment/3398466/+files/config.log
--
You received this bug notification because you are a member of Desktop
Packages
Public bug reported:
I'm trying to compile Wine from source but everytime i run ./configure i got at
the end of the log:
configure: libOSMesa development files not found (or too old), OpenGL rendering
in bitmaps won't be supported.
There was a bug filled in wine-bugs but they say is a problem i
34 matches
Mail list logo
