On October 10, 2003 08:17 pm, Steven Edwards wrote:
> Here are the templatates I have stated on for the website regarding
> porting WINE to other CPUs and Compilers. Please send any flames about
> spelling/grammer to \Device\NUL as I this is a work in progress. If you
> have worked on any of the fo
These logs doesnt show anything brilliant/remarkable to me.
Could this be an uninitialised pointer problem ?
--- Jerry Jenkins <[EMAIL PROTECTED]> a écrit :
> It's not necessary. I ask you the question just because that I am not
>
> quite familiar with the source :-(.
>
> The logs you provided
Yes, they work without problem.
I can provide logs/screen copy if needed.
It's not necessary. I ask you the question just because that I am not
quite familiar with the source :-(.
The logs you provided show that dsound or winealsa call alsa-lib with an
invalid device name. The line is
ALSA lib
Hello,
Here are the templatates I have stated on for the website regarding
porting WINE to other CPUs and Compilers. Please send any flames about
spelling/grammer to \Device\NUL as I this is a work in progress. If you
have worked on any of the following ports please send me the correct
information
Hi folks,
I have a big problem with the last version of wine. I have made 'make
clean', 'make distclean' and recompile everything and i still get a
segmentation fault !
I have deleted all my sources and made a new check out from cvs server.
After running wineinstall, i still get the segmentat
Mike Hearn <[EMAIL PROTECTED]> writes:
> I dunno how Linux specific this is, but it works pretty well and lets you
> make a relocatable binary every time. Would this be an acceptable 2nd
> implementation for init_argv0_path() that works when wine is invoked from
> the path also?
I don't think tha
On Fri, 10 Oct 2003, Alexandre Julliard wrote:
>> Depending on how you plan to fix the compilation failure, it might make
>> sense to have just one declaration at the top instead of several (and
>> thus several #ifdef's, in case they are needed for the fix) in functions?
> Well, maybe, but we can o
I've a lot of problems with textures in Windows OpenGL programs running
within wine(x) on my GeForce 2 Go. Also when scaling a wine-ed OpenGL
Programm over 640x480 the framerate immediately drops below 5 fps.
However exactly the same programms run well with my GeForce 2 Ultra card
within almost
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> ChangeLog
> Remove the no longer used SYMBOLFILE.
While you are at it you should remove LDDLLFLAGS too, it's going to
disappear very soon. This way we won't have to change every Makefile
twice.
--
Alexandre Julliard
[EMAIL PROTECTED]
Hi folks,
As I said, there are over 200 instances of {Local,Global,Heap,}ReAlloc that
need reviewing and/or fixing. We need to keep a close eye on these, so we
don't let some fall through the cracks.
I've compiled a list of all the places that need attention. We currently
have 225 such places. Be
Gerald Pfeifer <[EMAIL PROTECTED]> writes:
> Depending on how you plan to fix the compilation failure, it might make
> sense to have just one declaration at the top instead of several (and
> thus several #ifdef's, in case they are needed for the fix) in functions?
Well, maybe, but we can only tel
On Fri, 10 Oct 2003, Alexandre Julliard wrote:
>> Declare environ at the top, not inside functions.
> I must be missing something here. Why does this make a difference?
I don't remember chapter and verse of the standards, but this came up
some time ago on the GCC mailing lists (though, in hindsigh
Yes, they work without problem.
I can provide logs/screen copy if needed.
Note: all of them were compiled from sources (driver, lib, oss compat,
tools and utils)
> Do other programs that will call ALSA APIs such as alsamixer and
> aplay work properly?
>
=
Sylvain Petreolle (spetreolle_at_u
Geoff Thorpe <[EMAIL PROTECTED]> writes:
> But if mailman can't do it, there would still be other ways to organise
> this, only they would be uglier and trickier. Do we actually know yet if
> someone at winehq will "let this happen"? And likewise, would Alexandre
> (as the primary target of win
Gerald Pfeifer <[EMAIL PROTECTED]> writes:
> ChangeLog:
> Declare environ at the top, not inside functions.
I must be missing something here. Why does this make a difference?
--
Alexandre Julliard
[EMAIL PROTECTED]
Hi Alexandre,
I understand your idea and it makes perfect sense. Maybe the description of my
patch wasn't clear enough. And maybe I shouldn't have changed SetTextColor and
SetBkColor (that were actually the only callbacks that were well implemented on
both the driver side and the the GDI). But
FWIW: I'm away soon for a few days, so you'll have to continue this
without me (a fact which is no doubt to your infinite relief :-).
On October 10, 2003 11:27 am, Dimitrie O. Paun wrote:
> On Fri, 10 Oct 2003, Geoff Thorpe wrote:
[snip]
> I haven't dispatched you to the archives to be rude, but
I found out why I have got this crash for two days.
I have in my config file the following line
"uxtheme" = ""
to prevent wine from using the built in one.
It is what makes wine crash at startup. If I comment the line
I have no more crashes. It start happening two days ago with the changes
on n
On Fri, 10 Oct 2003, Geoff Thorpe wrote:
> The submission and processing of patches is not something totally alien to
> me, though the specific history and conclusions reached w.r.t. wine mail
> lists is. That said, you needn't crusade the inlining argument by
> dispatching me to the list archi
--- Gerald Pfeifer <[EMAIL PROTECTED]> wrote:
> I hope this is useful?
Brilliant, thanks a lot!
Jon
=
"Don't wait for the seas to part, or messiahs to come;
Don't you sit around and waste this chance..." - Live
[EMAIL PROTECTED]
__
Do you Yahoo!?
The New Y
On Fri, 10 Oct 2003, Jon Griffiths wrote:
>> http://rtp.freebsd.org/~gerald/
> Great stuff, cheers! The output format is fine, but would it be
> possible to rebuild the whole tree each night?
In fact the whole tree is rebuilt each night, but this was not really
clear from the log. If you check la
Hi,
--- Gerald Pfeifer <[EMAIL PROTECTED]> wrote:
> That's an excellent suggestion! I made the last log available
> right away and hacked the script to automatically publish logs
> from the daily builds from now on:
> http://rtp.freebsd.org/~gerald/
Great stuff, cheers! The output format is fi
My nightly autobuilder failed to build today, after I've had no
problems for several days. This seems to be due to yesterday's
changes in dlls/kernel:
process.o: In function `build_initial_environment':
wine/dlls/kernel/process.c:341: undefined reference to `environ'
wine/dlls/kernel/proces
On Thursday 09 October 2003 08:54 pm, Tom Hibbert wrote:
> Hi guys,
> I'm running DameWare Mini Remote Control under Wine here. This is a
> pretty cool setup as some of our clients
>
> have no windows servers (only linux), and the idea is that we can VNC to
> a Linux firewall or file server and the
On October 9, 2003 10:54 pm, Dimitrie O. Paun wrote:
> On October 9, 2003 09:58 pm, Geoff Thorpe wrote:
> > look/feel/use, like "wine-cvs". I would have personally thought that
> > attachments make more sense, because separating patches from text can
> > be ambiguous and it's not as easy to send mu
I have some code that can figure out the absolute address of the binary by
either:
a) Looking for itself in /proc/self/maps ... or
b) using r_map and /proc/self/exe
I dunno how Linux specific this is, but it works pretty well and lets you
make a relocatable binary every time. Would this be an acc
IANAL but here are some examples of things that I think are things that the
law was intended to protect:
1.A real-estate database with information on many different houses.
2.The database at e.g. amazon.com containing details about a whole bunch of
books
3.A database containing details of flights
There's source for a small regression test program at
http://www.securityfocus.com/bid/8395/exploit/
which checks to make sure DameWare's server is
giving unauthorized users administrator access :-)
Might be fun to see if that works against a
DameWare server running on Wine (if and when
wine is imp
> On Wed, 8 Oct 2003 21:53, Patrik Stridvall wrote:
>
> > The significant effort requirement is for EACH fact seen by ITSELF.
>
> This is certainly not the case in Australia, NZ and the UK.
So you can have protection on collections of truely trivial facts?
I severly doubt that. What legal purpos
29 matches
Mail list logo
