http://bugs.winehq.org/show_bug.cgi?id=3835
lionel.ulmer(a)free.fr changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wine-bugs(a)winehq.org
AssignedTo|wine-bugs(a)winehq.org |oliver_stieber(a)yahoo.co.uk
------- Additional Comments From lionel.ulmer(a)free.fr 2005-14-11 14:44 -------
Oliver,
You have a nice example of multi-threaded D3D9 application:
0009:trace:d3d:IWineD3DDeviceImpl_SetupTextureStates glEnable(...) call ok
device.c / 318
0009:trace:d3d:IWineD3DDeviceImpl_SetupTextureStates ----------------------->
Updated the texture at Sampler 0 to have new texture state information
000d:trace:d3d9:IDirect3DDevice9Impl_SetLight (0x5590bcc0) Relay
000d:trace:d3d:IWineD3DDeviceImpl_SetLight (0x59adad40) : Idx(0), pLight(0x5c2efacc)
Which of course leads to a crash in the GL driver.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.
http://bugs.winehq.org/show_bug.cgi?id=3835
------- Additional Comments From lionel.ulmer(a)free.fr 2005-14-11 14:14 -------
Could you attach a +d3d,+wined3d,+d3d9,+tid,+seh trace to this bug report ?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3835
willie(a)froq.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |download, NoAppDBEntry
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3397
aric(a)codeweavers.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
------- Additional Comments From aric(a)codeweavers.com 2005-14-11 13:44 -------
Working with the latest cvs tip (Nov 14 2005) and the version of picasa I just
downloaded (build 27.66,0) I do not see any evidence of this defect. It appears
the the "Folder Manager..." is working fine to me.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3051
------- Additional Comments From tlp(a)liquidx.org 2005-14-11 13:11 -------
Using msvcrt.dll as a workaround worked for me when attempting to update
Starcraft.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3408
dank(a)kegel.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |WORKSFORME
------- Additional Comments From dank(a)kegel.com 2005-14-11 10:53 -------
I solved this a couple weeks ago, but forgot to update this PR.
And for some reason, my post isn't in the usual wine-devel
archives. Here's a link to another archive:
http://marc.theaimsgroup.com/?l=wine-devel&m=112993474405336&w=2
and here's a copy of my post. The upshot is: libfreetype
wasn't found because the developer who built wine had
a funny setup, and was using 'acoc' to colorize the output
of ldd, and acoc corrupted the output of ldd.
-- snip --
Here's the strangest thing I've seen for a while.
I was tracking down why I could build Wine, but another guy
on the same machine could only build a slightly broken Wine that
gave the error
Wine cannot find the FreeType font library. To enable Wine to
use TrueType fonts please install a version of FreeType greater than
or equal to 2.0.5.
whenever you tried to use it.
The first clue was funny output from Wine's configure script,
though it was hard to see until I diff'd against good output,
and used cat -v to make invisible chars visible:
--- configure.log.good.txt 2005-10-20 10:57:21.000000000 -0700
+++ configure.log.bad.txt 2005-10-21 14:41:59.000000000 -0700
...
-checking for ldd... /usr/bin/ldd
-checking for -lX11 soname... libX11.so.6
-checking for -lXext soname... libXext.so.6
...
+checking for ldd... /home/mmoss/bin/ldd
+checking for -lX11 soname... libX11.so.6^[[0m
+checking for -lXext soname... libXext.so.6^[[0m
And what's that funny ldd?
And what are those escape sequences?
Turns the ldd is one wrapped by acoc (http://www.caliban.org/ruby/acoc.shtml)
which colorizes the output, which also explains the funny escape sequences.
This error went away when we stopped using acoc to colorize the
output of commands like ldd. We had been using acoc-0.5.2,
but the latest version (0.7.1) also exhibits the problem.
I hope this helps somebody else who's scratching their head
over strange build fHere's the strangest thing I've seen for a while.
I was tracking down why I could build Wine, but another guy
on the same machine could only build a slightly broken Wine that
gave the error
Wine cannot find the FreeType font library. To enable Wine to
use TrueType fonts please install a version of FreeType greater than
or equal to 2.0.5.
whenever you tried to use it.
The first clue was funny output from Wine's configure script,
though it was hard to see until I diff'd against good output,
and used cat -v to make invisible chars visible:
--- configure.log.good.txt 2005-10-20 10:57:21.000000000 -0700
+++ configure.log.bad.txt 2005-10-21 14:41:59.000000000 -0700
...
-checking for ldd... /usr/bin/ldd
-checking for -lX11 soname... libX11.so.6
-checking for -lXext soname... libXext.so.6
...
+checking for ldd... /home/mmoss/bin/ldd
+checking for -lX11 soname... libX11.so.6^[[0m
+checking for -lXext soname... libXext.so.6^[[0m
And what's that funny ldd?
And what are those escape sequences?
Turns the ldd is one wrapped by acoc (http://www.caliban.org/ruby/acoc.shtml)
which colorizes the output, which also explains the funny escape sequences.
This error went away when we stopped using acoc to colorize the
output of commands like ldd. We had been using acoc-0.5.2,
but the latest version (0.7.1) also exhibits the problem.
I hope this helps somebody else who's scratching their head
over strange build failures!
- Dan
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3834
tony_lambregts(a)telusplanet.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |download, NoAppDBEntry
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.