May 2002 - Wine-Devel - list.winehq.org

Re: [Bug 751] Changed - GetDiskFreeSpace should return >2GB on some systems

by Andreas Mohr

Hi all, could you have a look at bug #751 and check the values on your Windows version and add a comment to the bug on what your version does ? (please don't forget to only check for partitions > 2GB !!) Thanks ! On Thu, May 30, 2002 at 11:19:14PM -0500, wine-bugs(a)winehq.com wrote: > http://bugs.winehq.com/show_bug.cgi?id=751 > > *** shadow/751 Thu May 30 23:18:08 2002 > --- shadow/751.tmp.27844 Thu May 30 23:19:14 2002 > *************** > *** 25,27 **** > --- 25,31 ---- > the selected emulated version, or always return the actual free size. > > I'll attach a small program to obtain the return values from GetDiskFreeSpaceA. > + > + ------- Additional Comments From vberon(a)mecano.gme.usherb.ca 2002-05-30 23:19 ------- > + Created an attachment (id=150) > + Test program to obtain the return values of GetDiskFreeSpaceA -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://mohr.de.tt

May 31, 2002

Re: wine can't find regedit.exe.so when it is not on the path

by Andriy Palamarchuk

--- Alexandre Julliard <julliard(a)winehq.com> wrote: > Andriy Palamarchuk <apa3a(a)yahoo.com> writes: > > > I can't start just installed regedit manually, > > wine gets confused by symbolic links in the > windows > > directory: > > regedit.exe -> /usr/local/bin/regedit > > regedit.exe.so -> /usr/local/bin/regedit.so > > These symlinks should be removed too, they are no > longer necessary. As I remember the links in the first place were created for apps which can try to load regedit and other Wine apps using full path. Do you think we don't need this? Andriy __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com

May 31, 2002

Re: PATCH: libntddl.so not found

by Dustin Navea

--- Marcus Meissner <marcus(a)jet.franken.de> wrote: > On Fri, May 31, 2002 at 08:12:24AM -0700, Dustin > Navea wrote: > > Hmmm, I found some problems with this: > > > > +print NEWMAKE <<EOF; > > > > shouldn't that be printf ? > > No, there are no % formatting strings inside. DOH! ;) > > + \@if test -f /etc/ld.so.conf -a -z "`grep > \$(libdir) > > /etc/ld.so.conf`" ; \\ > > > > shouldn't that be \$(LIBDIR) > > No, I am evaluating the libdir Make variable. DOH again! ;) > > + echo " Add the line '\$(libdir)' to > > /etc/ld.so.conf" ; \\ > > > > I think that escaping the $ in this line is > > unnecessary as it this prints "$(libdir)" instead > of > > the contents of that variable, and also libdir > should > > be capitalized there too... > > > perl expands that to $(libdir), which make expands > to /usr/local/lib. > > If I would have use $(libdir) perl would have > printed $( and libdir). bah > > + echo " export > > LD_LIBRARY_PATH=\$(libdir):\$LD_LIBRARY_PATH" ; \\ > > > > Same as above except that it doesn't apply to > > \$LD_LIBRARY_PATH as we want "$LD_LIBRARY_PATH" to > be > > printed... > > Hmm, LD_LIBRARY_PATH is not printed correctly. But I > do not know > how to let make escape that correctly. hmm, that is interesting, i have seen situations in other projects where using \escape sequences didn't work, 1 of them actually worked around it by using the same symbol ($$ instead of \$) i dont know how they did it but that is the only time that i have ever seen it and never again... may as well give it a shot > Btw, why didn't you try the code before complaining? Like i'm going to download the code, go home, test it out and come back up here just to complain...yea right ;) -Dustin __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com

May 31, 2002

Re: wine can't find regedit.exe.so when it is not on the path

by Dustin Navea

--- Andriy Palamarchuk <apa3a(a)yahoo.com> wrote: > > --- Dustin Navea <speeddymon(a)yahoo.com> wrote: > <skipped> > > I do believe that you are running the wrong > > regedit... > > is /prj/wine your wine install dir or did you > > install > > to the default wine install dir (/usr/local/bin)? > > No, this is not wine install dir - this is wine > source > dir. And wineinstall runs not the installed regedit, > it runs the one, compiled in the source three. > This is how regedit path is defined in wineinstall: > > REGEDIT=programs/regedit/regedit > > I don't think there are other options of > interpreting > location of regedit. > I did forget that wineinstall runs regedit from the source wine directory... > > If > > you installed to the default winr install dir, run > > that one... I also ran into the problem of "not > > accessible from a configured dos drive" for the > wine > > progs, so I added a symlink to the .exe and the > > .exe.so in my fake c drive windows directory and > > everything worked like a charm... > > wineinstall script should run regedit from the > source > tree succesfully or it should be changed to run it > from /usr/local/bin directory. > Agreed, I would say that probably it would be better to go ahead and call it from the wine installed dir (maybe not always /usr/local/bin) since regedit isnt called until way after make install, so the binary is guaranteed to be already installed... -Dustin __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com

May 31, 2002

Re: wine can't find regedit.exe.so when it is not on the path

by Alexandre Julliard

Andriy Palamarchuk <apa3a(a)yahoo.com> writes: > I can't start just installed regedit manually, > wine gets confused by symbolic links in the windows > directory: > regedit.exe -> /usr/local/bin/regedit > regedit.exe.so -> /usr/local/bin/regedit.so These symlinks should be removed too, they are no longer necessary. -- Alexandre Julliard julliard(a)winehq.com

May 31, 2002

Re: Idea for people with priveleges

by Dustin Navea

--- Andriy Palamarchuk <apa3a(a)yahoo.com> wrote: > > --- Dustin Navea <speeddymon(a)yahoo.com> wrote: > > Well, AFAIK, there isn't reall a QA team, and if > > there > > is, they aren't checking out the bugs, because > > several > > bugs marked as resolved for over a year weren't > > closed > > until I went in and closed them.... > > Agree, we can simplify the things for now - skip > VERIFIED and RESOLVED steps in most cases - just > close > the bugs. > We can change the process later. > > Andriy > That is why I started this thread, we cant "just close the bugs" we have to resolve them first... We need 3 more options, probably would be easiest to implement in BugZilla 2.11: Close as Unresolved More information needed from User More testing Needed __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com

May 31, 2002

Re: Problem with 64-bit file functions declarations

by Alexandre Julliard

Andriy Palamarchuk <apa3a(a)yahoo.com> writes: > My lack of understanding - what is correct approach in > Winelib applications - to use msvcrt or native > functions? > > I always thought that correct approach is to use > msvcrt ones. Unless you depend on msvcrt-specific features, it's better to use the Unix C library. It will use less memory and load faster. -- Alexandre Julliard julliard(a)winehq.com

May 31, 2002

Re: Problem with 64-bit file functions declarations

by Dustin Navea

--- Andriy Palamarchuk <apa3a(a)yahoo.com> wrote: > I'm researching an issue when started regedit.exe > fails to export registry. This started to happen > after > Alexandre's patch which included "config.h" in the > regedit source file. > > I found out this problem was triggered by > declaration > > #define _FILE_OFFSET_BITS 64 > > in config.h. The test case: > > ******************************************** > /* Set this to 64 to enable 64-bit file support on > Linux */ > #define _FILE_OFFSET_BITS 64 > > #include <stdio.h> > #include <windows.h> > > void test_write(void) > { > FILE *f = fopen("1.reg", "w"); > printf("sizeof FILE: %d\n", sizeof(FILE)); > fputs("DEBUG1\n", f); > fclose(f); > } > > int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE > hPrevInstance, > LPSTR lpCmdLine, int nCmdShow) > { > test_write(); > exit(0); > } > ******************************************** > > Comment out the macro definition and it works, with > macro it creates file of 0 length. > With the defined macro many file functions are > defined > as functions for 64-bit access and are linked to the > native platform calls instead of msvcrt ones. > > Differences in precompilation output: > > Without macro: > > # 203 "/usr/include/stdio.h" 3 > extern FILE *fopen (__const char *__restrict > __filename, > __const char *__restrict > __modes) > ; > > With macro: > > # 211 "/usr/include/stdio.h" 3 > extern FILE *fopen (__const char *__restrict > __filename, > __const char *__restrict > __modes) > __asm__ ("" "fopen64"); > > The same happens for some other file functions. > What is the correct fix for this problem? > > Andriy > Hate to say it, but maybe we need yet *another* #ifdef... something like #ifdef __IA64__ #define _FILE_OFFSET_BITS 64 #endif yes i know that __IA64__ isnt anything but i was just using it for example... __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com

May 31, 2002

Re: Problem with 64-bit file functions declarations

by Andriy Palamarchuk

--- Alexandre Julliard <julliard(a)winehq.com> wrote: > Andriy Palamarchuk <apa3a(a)yahoo.com> writes: > > > The same happens for some other file functions. > > What is the correct fix for this problem? > > Just remove msvcrt from the import list, it isn't > needed (or if you > really want to use msvcrt, then you have to use the > msvcrt headers too > instead of the libc ones). My lack of understanding - what is correct approach in Winelib applications - to use msvcrt or native functions? I always thought that correct approach is to use msvcrt ones. Andriy __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com

May 31, 2002

Re: wine can't find regedit.exe.so when it is not on the path

by Alexandre Julliard

Andriy Palamarchuk <apa3a(a)yahoo.com> writes: > wineinstall fails because wine can't find > regedit.exe.so. > Obviously, the wine source directory does not exist in > path of just created config file. I'd say that wineinstall should run the installed wine binaries, not the ones from the source dir. -- Alexandre Julliard julliard(a)winehq.com

May 31, 2002