On Mon, 2003-11-17 at 10:34, Kevin Cousins wrote:
> Hello,
>
> Given that I've got a situation in which my WineLib application (thank
> you for your help earlier in the year) needs to run against the Win32
> QuickTime components, then in my development environment (RH9), I can
> quite happily run
Thanks, that seemed to fix it.
Jeremy Shaw.
On Nov 16, 2003 12:42 PM, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> Jeremy Shaw <[EMAIL PROTECTED]> writes:
>
> > Hopefully someone who understands linker magic better than me can come
> > up with a better fix...
>
> I think adding --expor
Hello,
Given that I've got a situation in which my WineLib application (thank
you for your help earlier in the year) needs to run against the Win32
QuickTime components, then in my development environment (RH9), I can
quite happily run the downloaded QuickTime installer
QuickTimeInstaller.exe to
Jeremy Shaw <[EMAIL PROTECTED]> writes:
> Hopefully someone who understands linker magic better than me can come
> up with a better fix...
I think adding --export-dynamic to the link should be
enough. Something like this should do the trick:
Index: configure.ac
==
Rein Klazes <[EMAIL PROTECTED]> writes:
> The maker seem to think that the handle must be closed both by
> sub-thread and main thread before it is removed. That is how I read the
> traces as well. So that is not true?
No, handles are process wide, so closing a handle once closes it for
the whole
Hello,
I have a work-around -- I put loader/kthread.c in its own shared library and things
work again:
I changed:
distcc -c -I. -I. -I../include -I../include-Wall -mpreferred-stack-boundary=2
-fno-strict-aliasing -gstabs+ -Wpointer-arith -O2 -g -o kthread.o kthread.c
to:
distcc -shared
No problem, I bring up to date again. I only wanted to see as it was being the
WineCfg and as it would be in Portuguese. Who wants to see apply the patch.
Em Dom 16 Nov 2003 08:55, Mike Hearn escreveu:
> Well, I don't have any real problem with it, but as I said before it's
> pretty pointless IM
Well, I don't have any real problem with it, but as I said before it's
pretty pointless IMHO. The GUI is going to start changing again when I
next get time to work on it (unfortunately not anytime soon in the
foreseeable future), so you'll have to update it all over again.
What winecfg needs now i
On Sat, 15 Nov 2003 16:41:44 -0800, you wrote:
> Rein Klazes <[EMAIL PROTECTED]> writes:
>
> > I looked at many of these sequences. In all of them the subthread
> > finished well before the main thread executed its Wait. I was looking
> > for timing differences between the processing of the two t
