wine-devel August 2003

wine-devel@winehq.org

124 participants
293 discussions

Viruses in the wine-devel archive ??
by PETREOLLE Sylvain 22 Aug '03

22 Aug '03

Someone on the list has the virus Sobig.f and sent it to wine-devel on Wed Aug 20 2003 - 23:18:18 CDT We MUST remove the infected message from the wine-devel archive. Cordialement, PETREOLLE Sylvain #DMIT/DATO/OPS (exploit(a)gefco.fr ) (+33-1 49 05) 29 29

9 12

Re: wcmd patch
by Eric Pouech 22 Aug '03

22 Aug '03

Oleg Prokhorov wrote: > Hello wine-patches, > > Changelog: > Fixes two problems: > GPF when no extension was specified. > No handles were inherited in CreateProcess, all child console programs were silent > the second part is wrong. a child process should inherit its parent input/output stream even if we don't inherit all the handles. But the bug still exist as of today. I'll look into it. A+ -- Eric Pouech

1 1

About spam
by Sylvain Petreolle 22 Aug '03

22 Aug '03

I have an evidence that some robots can grab our email adress, even with our mangling process on winehq. I used my work adress only onto wine-devel and got spammed last week. ===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 alias upsf='false ; while [ $? -ne 0 ] ; do cvs update -APd ; done 2>&1 |tee cvslog' "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

3 2

Work on building comctl32 with MS_VC and MS_VC headers
by Steven Edwards 22 Aug '03

22 Aug '03

I have made a log of my attempts to fix comctl32.dll with the MS_VC headers but I am going to have to call it a day. If anyone has time and a copy of MS_VC can you take a look and tell me whats going on? The log of my progress is here: http://mail.gleneagle.net/sedwards/comctl32_msvc.txt It may just be something as simple as WINE having most of the headers included in the wrong order or included in places where they shouldnt be such as stdarg in winbase.h and a lack of winbase.h. Thanks Steven

2 1

New infected email
by puoti＠inwind.it 22 Aug '03

22 Aug '03

This sould go too. http://www.winehq.org/hypermail/wine-patches/2003/08/0224.html

2 1

Re: Viruses in the wine-devel archive ??
by puoti＠inwind.it 22 Aug '03

22 Aug '03

Who says he is infected?I've got some messages from emial servers saying that I've sent infected emails, but I know that I aren't infected because I only use webmail and only on linux,my mail server is a mixed linux/solaris, so probably a robot finds emial addresses and sends infected emails from a mail server with a fake origin email address.

1 0

Virus Alert - Please scan your Windows boxes
by Jeremy Newman 22 Aug '03

22 Aug '03

We've gotten a few viruses sent out to the mailing lists in the last few weeks. This is a friendly reminder to please scan your Windows boxes (since, I know some of you use them for email, shame on you!). There is a FREE virus scanner out there that removes these any many other worms. get it here: http://www.avast.com/ note: for some reason their download pages 404, they did work last night, so I assume they took them down due to load. They should be back up soon. If someone knows of a mirror please let us know. -- Jeremy Newman <jnewman(a)codeweavers.com> CodeWeavers, Inc.

2 1

Problems building dlls for use with winelib (was: spec file syntax and automated generation)
by "Martin Tröster" 22 Aug '03

22 Aug '03

Hi Jon, On Thu, 21 Aug 2003 02:34:00 -0700 (PDT) Jon Griffiths <jon_p_griffiths(a)yahoo.com> wrote: > wine-devel is the place for any development issues, including > problems with Winelib. Since someone may have the same > problem(s) in the future, I'm also sending this to wine-devel > (it serves as an issues archive for common problems). Allright, I thought wine-devel was more concerned with internal development, not the development of winelib-applications as well. Perhaps you could put that on the description of the wine-devel mailing list on WineHQ? Suggesting issues regarding WineHQ.com, I would like you to add datestamps and/or version numbers to any documentation. Since I did not get any responses to my questions on wine-users, I post the problems of building winelib-dlls again here. Hopefully someone of you can give me a hint what exactly I'm doing wrong. I suppose it's something basic, but I'm currently stuck with this problem. So here we go: =================================================== Begin forwarded message: Date: Tue, 19 Aug 2003 11:41:36 +0200 From: Martin Troester <TroyMcClure(a)web.de> To: wine-users(a)winehq.com Subject: Problems building dlls for use with winelib Hi, I am currently having trouble building the DLLs of an application ported from Win32 to Winelib - compiling, thanks to some hints from Dimi O. Paun, now works fine, only(?) the final linking step fails. Since Winelib-documentation is unfortunately pretty outdated, I tried to orientate myself on the makefiles of the Winelib dlls in the cvs /wine/dlls/ directory. I tried the following build-steps: 1. Build all object files with winegcc/wineg++ and the following flags: > -W -g -O0 -I/ -I/usr/include/wine -D_DEBUG -DWIN32 -D_WINDOWS > -DNOARRAYMACROS -DBUILD_DLL -fPIC 2. relocate symbols (took this one from the makefile of advapi32.dll): > ld -r $(OBJS) -o libdll.tmp.so && strip --strip-unneeded libdll.tmp.so 3. build spec file with the previously generated temporary library, the imported libraries from winelib and with a spec-file containing the functions to be exported from the dll and compile it (omitted here) with the same flags as used above for the original source files: > winebuild -fPIC -L/usr/local/lib/wine -lntdll -lkernel32 -luser32 > -lgdi32-lcomdlg32 -lcrtdll -o libdll.spec.c --spec libdll.spec > libdll.temp.o Finally, I (at least try to) tie everything together in a single library: > winegcc -shared -Wl,-soname,libdll.so -DSTRICT -D_REENTRANT > -L/usr/local/lib/wine -lntdll -lkernel32 -luser32 -lgdi32 -lcomdlg32 > -lstdc++ -lcrtdll -lgcc_s -lm $(OBJS) The result is the following warnings and errors: > (1) libdll.spec.o(.rodata+0x0): multiple definition of `dllname' > /tmp/wappX6tcsm.spec.o(.rodata+0x0): first defined here > (2) /usr/bin/ld: Warning: size of symbol `dllname' changed from 10 in > /tmp/wappX6tcsm.spec.o to 12 in > (3) /tmp/wappX6tcsm.spec.o(.text+0x1004a): In function > `__wine_exe_main':: undefined reference to `main' Regarding (1) and (2): I cannot make a sense on why I should have made a mistake here - it seems as if we have two spec-files here, one generated by myself, and one automatically (the one in /tmp/wapp*.spec.o). Why's this happening? And why are we coping with a __wine_exe_main in (3)? I am trying to build a dll, so something's going totally wrong here... Thinking about problems with the spec-file, I replaced my self-written file with functions to be exported with an entirely empty one. However, the errors stay the same. Furthermore, I thought I had to use --entry as an option to specify my special entry point (do I still have to change it from dllmain on Win32 to a unique name for Linux/Unix to avoid duplicate names in libraries, or does winebuild handle this somehow?). Using or not using it does not make any difference... You see, I am a little bit desperate about this thing, having come pretty far, but now seeming to fail on the last meters. So any help (on this list or if you think it's too specific to my private mail) would be really, really appreciated. If I find some time, I will volunteer to write a short step-by-step guide based on my observations, if this is any help for you to avoid dumb questions like these ;-) ================================================== Begin forwarded message: Date: Tue, 19 Aug 2003 12:47:11 +0200 From: Martin Troester <TroyMcClure(a)web.de> To: wine-users(a)winehq.com Subject: Re: Problems building dlls for use with winelib To simplify the problem, I just created a really simple DLL, just exporting one function: ============ testlib.c ============== void tstfunc (void); void tstfunc (void) { int a=7; //printf ("Hello\n"); } ===================================== The testlib.spec file exports this function the following way: ========== testlib.spec ============= @ stdcall tstfunc() tstfunc ===================================== Compiling it like explained before, this is what happens (in this case no .exe is assumed, but it still fails, and I do not know why...) (1) winegcc -W -g -O0 -I/usr/include/wine -fPIC -o testlib.o -c testlib.c (2) ld -r testlib.o -o libtest.dll.temp.o (3) strip --strip-unneeded libtest.dll.temp.o (4) winebuild -fPIC -o testlib.spec.c --spec testlib.spec libtest.dll.temp.o winegcc -W -g -O0 -I/usr/include/wine -o testlib.spec.o -c testlib.spec.c (5) gcc -shared -Wl,-Bsymbolic,-z,defs testlib.o testlib.spec.o -o libtest.dll.so (OUTPUT) testlib.spec.o(.text+0x1002d): In function `__wine_spec_testlib_dll_init':/home/mt/testlib/testlib.spec.c:156: undefined reference to `__wine_dll_register' collect2: ld returned 1 exit status make: *** [libtest.dll.so] Error 1 Once again, neither changing the spec-file (removing the function from being exported) nor adding tstfunc as an entry-point changes anything... Thus, I assume I am getting something very basic wrong here. Since this may be of some help in the actual dll building, I would again appreciate any hints on solving these errors... ======================================================= Cheers, Martin __________________________________________________________________________ Die sicherste Form der Kommunikation: E-Mails verschluesseln, Spam-Filter, Adressverifizierung, digitale Unterschrift: http://freemail.web.de

2 1

RE: Int21 : Dont reset systematically CFLAG
by PETREOLLE Sylvain 22 Aug '03

22 Aug '03

Doing some research in int21.c shows that many functions that rely on CFLAG dont set it when they are in error state. IMHO many DOS programs are already broken today since these functions appear to be successfull at every moment. For example : INT21_FileDateTime (handler for function 0x57, file attributes) -----Message d'origine----- De : Jukka Heinonen [mailto:jhei@iki.fi] Envoyé : lundi 18 août 2003 20:14 À : wine-devel(a)winehq.com Objet : Re: Int21 : Dont reset systematically CFLAG Sylvain Petreolle wrote: > Dont reset systematically CFLAG when calling the int 21 handler. > Some functions dont change it. This patch must not be applied because it is highly likely that it will break almost all DOS programs. Fix itself is correct but before this patch can be applied it must be made sure that all functions that are supposed to reset CFLAG really reset it. -- Jukka Heinonen <http://www.iki.fi/jhei/>

2 1

Re: PATCH - winnt.h move non-standard language IDs to wine/port.h
by Dmitry Timoshkov 22 Aug '03

22 Aug '03

"Steven Edwards" <Steven_Ed4153(a)yahoo.com> wrote: > -#define LANG_DIVEHI 0x65 > -#define LANG_GALICIAN 0x56 > -#define LANG_KYRGYZ 0x40 > -#define LANG_MONGOLIAN 0x50 > -#define LANG_SYRIAC 0x5a The above defines present in winnt.h from the Platform SDK. You have to update MinGW headers, not to remove those defines from Wine headers. -- Dmitry.

2 1

← Newer
1
...
10
11
12
13
14
15
16
...
30
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel August 2003