Re: vsnprintf: glibc and win32 not compatible

2004-03-08 Thread Jesse Allen
On Mon, Mar 08, 2004 at 08:28:38PM +0100, Joerg Mayer wrote: > Ethereal brings its own version of (v)snprintf in form of the snprintf.[hc] > files. While Ethereal is GPLed, the files in question are LGPLed. The > files do not originate with Ethereal but I don't remember where they > came from. >

Re: Warn If GetProcAddress Fails

2004-03-08 Thread Kevin Koltzau
Many apps dynamically bind to entry points to determine if features in Windows are available as well, This may cause quite a few apps to report huge numbers of warnings when there is actually nothing wrong On Monday 08 March 2004 08:44 pm, Robert Shearman wrote: > Many applications dynamically bin

Re: Wine as shared library patch

2004-03-08 Thread Alexandre Julliard
Miguel de Icaza <[EMAIL PROTECTED]> writes: > Could we get this in the official Wine distribution? Peter's patch > includes the Makefile and configure magic as well (the rest could be > dropped). I would really prefer for you to ship it yourself. This is not a general solution, and we don't want

Re: Wine as shared library patch

2004-03-08 Thread Miguel de Icaza
Hello, > Miguel de Icaza <[EMAIL PROTECTED]> writes: > > > Our patch is simple, and we lack the experience to work on Wine, TEB and > > what not.We just do not have the time to learn everything there is > > to Wine. > > Something along these lines should do the trick: I tested something li

Cygwin under Wine

2004-03-08 Thread Erik de Castro Lopo
Hi all, I'm interested in running Cygwin under Wine. When trying to run the cygwin bash.exe I get the following: fixme:console:SetConsoleCtrlHandler (0x61025d10,0) - no error checking or testing yet fixme:console:SetConsoleCtrlHandler (0x61025d10,1) - no error checking or testing yet fixme:ntdll

Re: Wine as shared library patch

2004-03-08 Thread Alexandre Julliard
Miguel de Icaza <[EMAIL PROTECTED]> writes: > Our patch is simple, and we lack the experience to work on Wine, TEB and > what not.We just do not have the time to learn everything there is > to Wine. Something along these lines should do the trick: #include #include #include #include #i

Re: Contribution offer: Localization work

2004-03-08 Thread Christian Britz
[Shachar and Ivan wrote details regarding further tasks] Thank you very much, I think I will quit my regular job now ... ;-)

Re: Contribution offer: Localization work

2004-03-08 Thread Christian Britz
Shachar Shemesh schrieb: [FSF wont accept translations] Full Ack.

Re: Contribution offer: Localization work

2004-03-08 Thread Christian Britz
Hi Fabi, you are coming from Ticino? Very nice region, have been there some times! :-) Fabian Cenedese schrieb: Binärdateien), unter Unix auszuführen. Es besteht aus einem Programm- Lader, der Microsoft Windows-Binärdateien lädt und ausführt, sowie einer Library (Winelib genannt), die Aufrufe de

Re: _ftime patch

2004-03-08 Thread Uwe Bonnes
> "Hans" == Hans Leidekker <[EMAIL PROTECTED]> writes: Hans> On Monday 08 March 2004 07:56, Johannes Gajdosik wrote: >> I found that the _ftime-function only returns seconds, not >> milliseconds. Therefore I would like to send you a patch that uses >> gettimeofday(). Hans

Re: Wine as shared library patch

2004-03-08 Thread Miguel de Icaza
hello,m > > Having Wine set up the TEB and stack environment and actually call our > > WinMain and us then trying to 'undo' that in WinMain creates potential for > > future breakage of our library, in case you change something related to > > the TEB & stack. > > The TEB & stack layout are dictate

Re: _ftime patch

2004-03-08 Thread Hans Leidekker
On Monday 08 March 2004 07:56, Johannes Gajdosik wrote: > I found that the _ftime-function only returns seconds, not milliseconds. > Therefore I would like to send you a patch that uses gettimeofday(). Your efforts are appreciated but an implementation that uses Win32 API's would be better since

Re: vsnprintf: glibc and win32 not compatible

2004-03-08 Thread Joerg Mayer
On Mon, Mar 08, 2004 at 10:15:33AM -0800, Alexandre Julliard wrote: > Probably 3), but I don't think you want to start with the glibc code, > it's fairly ugly code, with many dependencies on glibc internals and > gcc-specific things. Hopefully we can find a more portable > implementation somewhere

Re: vsnprintf: glibc and win32 not compatible

2004-03-08 Thread Bill Medland
On March 8, 2004 10:54 am, Bill Medland wrote: > On March 8, 2004 10:15 am, Alexandre Julliard wrote: > > Mike Hearn <[EMAIL PROTECTED]> writes: > > > On Sun, 07 Mar 2004 19:32:39 -0700, Jesse Allen wrote: > > >> 1) Create our own vsnprintf version from scratch (fairly difficult) > > >> or > > >

Re: vsnprintf: glibc and win32 not compatible

2004-03-08 Thread Bill Medland
On March 8, 2004 10:15 am, Alexandre Julliard wrote: > Mike Hearn <[EMAIL PROTECTED]> writes: > > On Sun, 07 Mar 2004 19:32:39 -0700, Jesse Allen wrote: > >> 1) Create our own vsnprintf version from scratch (fairly difficult) > >> or > >> 2) Create a wrapper for glibc's vsnprintf that translate

Re: vsnprintf: glibc and win32 not compatible

2004-03-08 Thread Ryan Underwood
On Mon, Mar 08, 2004 at 10:48:31AM +, Mike Hearn wrote: > On Sun, 07 Mar 2004 19:32:39 -0700, Jesse Allen wrote: > > 1) Create our own vsnprintf version from scratch (fairly difficult) > > or > > 2) Create a wrapper for glibc's vsnprintf that translates win32ish format > > statements into

Re: vsnprintf: glibc and win32 not compatible

2004-03-08 Thread Alexandre Julliard
Mike Hearn <[EMAIL PROTECTED]> writes: > On Sun, 07 Mar 2004 19:32:39 -0700, Jesse Allen wrote: >> 1) Create our own vsnprintf version from scratch (fairly difficult) >> or >> 2) Create a wrapper for glibc's vsnprintf that translates win32ish format >> statements into a glibc friendly one. (n

Re: Wine as shared library patch

2004-03-08 Thread Alexandre Julliard
"Peter Dennis Bartok" <[EMAIL PROTECTED]> writes: > Having Wine set up the TEB and stack environment and actually call our > WinMain and us then trying to 'undo' that in WinMain creates potential for > future breakage of our library, in case you change something related to > the TEB & stack. The

Re: Wine as shared library patch

2004-03-08 Thread Peter Dennis Bartok
Alexandre, et. al, Our WinMain doesn't get called because our patch prevents it. If it were to get called, we'd be on a different (Wine-created) stack, with all kinds of things that are hard to undo, like the exception handling, etc. The goal of my patch was to have minimal impact on Wine, and al

Re: Wine as shared library patch

2004-03-08 Thread Miguel de Icaza
Hello, > >> Perhaps this could be changed to a static variable in process.c > > Wouldn't that make it rather hard to be set from outside process.c? I > > need to set it from wine-sharedlib.exe.so > > It seems to me that you could simply do a longjmp() out of your > WinMain, and then you wouldn't

Re: Wine as shared library patch

2004-03-08 Thread Miguel de Icaza
Hey, > > Well, the issue is that our WinMain is never called, and we would > > rather not depend on this in our patch, but instead get the small > > global that says `Hey Wine, just return'. > > The global variable thing is ugly; we could export a different entry > point instead, but I'm not sure

RtlGetDaclSecurityDescriptor crash on NULL pointer

2004-03-08 Thread Bobby Bingham
Installing winamp5 with winver=winxp reveals that the wma installer calls GetSecurityDescriptorDacl with pSecurityDescriptor == NULL, which then calls RtlGetDaclSecurityDescriptor, which immediately dereferences it and crashes. Reading MSDN indicates that pSecurityDescriptor may be NULL, but I don

Re: Contribution offer: Localization work

2004-03-08 Thread Shachar Shemesh
Ivan Leo Murray-Smith wrote: Look at the programs directory, most programs can be translated. You're usually looking for a De.rc file, if it's missing, make a second copy of the En.rc file, and call it De.rc. Now translate the strings in the file. You then have to edit the header file, this may be

Re: Contribution offer: Localization work

2004-03-08 Thread Shachar Shemesh
Fabian Cenedese wrote: Wine ist Freie Software, die unter der GNU LGPL veröffentlicht wird; Bitte lesen Sie die Details in der Datei LICENSE nach. If there is a translated Readme shouldn't there also be a translated licence file? No. The FSF cannot approve any translation as legally binding,

Re: vsnprintf: glibc and win32 not compatible

2004-03-08 Thread Mike Hearn
On Mon, 08 Mar 2004 11:59:55 +0100, Uwe Bonnes wrote: > Another option is to extend the glibcv version and try to get that version > into glibc... a) It's not portable to non-glibc systems then b) I take it you never tried to get patches into glibc before ;) I mean if you think you can convince U

Re: vsnprintf: glibc and win32 not compatible

2004-03-08 Thread Uwe Bonnes
> "Mike" == Mike Hearn <[EMAIL PROTECTED]> writes: Mike> On Sun, 07 Mar 2004 19:32:39 -0700, Jesse Allen wrote: >> 1) Create our own vsnprintf version from scratch (fairly difficult) >> or 2) Create a wrapper for glibc's vsnprintf that translates win32ish >> format statements i

Re: vsnprintf: glibc and win32 not compatible

2004-03-08 Thread Mike Hearn
On Sun, 07 Mar 2004 19:32:39 -0700, Jesse Allen wrote: > 1) Create our own vsnprintf version from scratch (fairly difficult) > or > 2) Create a wrapper for glibc's vsnprintf that translates win32ish format > statements into a glibc friendly one. (not too bad and smaller patch) We > could lat

Re: Contribution offer: Localization work

2004-03-08 Thread Fabian Cenedese
>Binärdateien), unter Unix auszuführen. Es besteht aus einem Programm- >Lader, der Microsoft Windows-Binärdateien lädt und ausführt, sowie >einer Library (Winelib genannt), die Aufrufe der Windows API unter >Verwendung der entsprechenden Unix- oder X11-Gegenstücke implementiert. I take it that th