- Wine-Devel - list.winehq.org

Re: set_thread_buffer
by Marcus Meissner May 31, 2001

May 31, 2001

On Thu, May 31, 2001 at 01:12:14PM -0400, =?iso-8859-1?Q?G=E9rard_Patel_=3Cgerard.patel=40nerim.net=3E?=(a)tourian.nerim.net wrote: > At 01:24 30/05/2001 +0200, you wrote: > (yet another self followup) > > >Since the commits of last night, every app I have tried only says : > > > >wine client error:0x80675a8: set_thread_buffer failed with status c000000d Hmm, can you do 'nm file/file.o|grep stat64' and see if we are including stat64 there? > >with apps that usually work fine. > I have still the problem; I have downloaded a fresh tree from winehq > to make sure it was not a random event. > > I don't have much time to debug until next weekend, but I have done > a bit of searching : this does not happen on my newest computer, a > Mandrake 8 with glibc 2.2. It happens with my other box, a Suse 6.1 > with a manually upgraded glibc 2.1.3 (I use it without this problem since > months) > > The problem occurs in the mmap call in the server subroutine, the parameters > being > size=8192, fd=8,offset=0. > > Has anyone compiled cvs since 3 days with glibc 2.1.3 ? I have build RPMs for OpenLinux eDesktop 2.4, which is kernel 2.2.14 and glibc 2.1.3, and sol.exe still works. You can try them from http://www.lst.de/~mm/wine.html if you want to. Ciao, Marcus

2 1

Re: set_errno patch
by Alexandre Julliard May 31, 2001

May 31, 2001

Francois Gouget <fgouget(a)free.fr> writes: > MSVCRT__set_errno should be able to set errno to 0. It's called at > least once explicitly with 0 in dir.c, but many other times it is > called with a GetLastError() that may return 0. I don't think it is ever correct to set errno to 0. Code that does that should be fixed to provide a valid error code instead. -- Alexandre Julliard julliard(a)winehq.com

1 0

FreeType autoconf checks - please test
by Ian Pilcher May 31, 2001

May 31, 2001

This works on my system (Red Hat 7.1 with FreeType 2.0.1). Please try it on other variants and let me know if it works. -- ======================================================================== Ian Pilcher ian.pilcher(a)home.com ======================================================================== diff -urN ../wine-20010529cvs/configure.in ./configure.in --- ../wine-20010529cvs/configure.in Thu May 31 09:16:57 2001 +++ ./configure.in Thu May 31 09:19:41 2001 @@ -402,8 +402,21 @@ wine_cv_msg_freetype=yes else AC_DEFINE(HAVE_FREETYPE) - FREETYPELIBS=`$ft_devel --libs` - FREETYPEINCL=`$ft_devel --cflags` + FREETYPELIBS=`$ft_devel --libs` + FREETYPEINCL=`$ft_devel --cflags` + ft_incl_dir=${FREETYPEINCL#-I} + old_c_include_path="$C_INCLUDE_PATH" + C_INCLUDE_PATH="$ft_incl_dir:$C_INCLUDE_PATH" + export C_INCLUDE_PATH + ft_incl_dir=$ft_incl_dir/freetype + AC_CHECK_HEADER($ft_incl_dir/freetype.h,AC_DEFINE(HAVE_FREETYPE_H)) + AC_CHECK_HEADER($ft_incl_dir/ftglyph.h,AC_DEFINE(HAVE_FTGLYPH_H)) + AC_CHECK_HEADER($ft_incl_dir/tttables.h,AC_DEFINE(HAVE_TTTABLES_H)) + AC_CHECK_HEADER($ft_incl_dir/ftnames.h,AC_DEFINE(HAVE_FTNAMES_H)) + AC_CHECK_HEADER($ft_incl_dir/ftsnames.h,AC_DEFINE(HAVE_FTSNAMES_H)) + AC_CHECK_HEADER($ft_incl_dir/ttnameid.h,AC_DEFINE(HAVE_TTNAMEID_H)) + C_INCLUDE_PATH="$old_c_include_path" + export C_INCLUDE_PATH wine_cv_msg_freetype=no fi fi diff -urN ../wine-20010529cvs/dlls/wineps/truetype.c ./dlls/wineps/truetype.c --- ../wine-20010529cvs/dlls/wineps/truetype.c Thu May 31 09:17:26 2001 +++ ./dlls/wineps/truetype.c Thu May 31 09:17:56 2001 @@ -9,11 +9,30 @@ #ifdef HAVE_FREETYPE +/* + * These stupid #ifdefs should work for FreeType 2.0.1 and 2.0.2. Beyond that + * is anybody's guess. + */ + +#ifdef HAVE_FREETYPE_H #include <freetype/freetype.h> -#include FT_NAMES_H -#include FT_TRUETYPE_NAMES_H -#include FT_TRUETYPE_TABLES_H -#include FT_GLYPH_H +#endif +#ifdef HAVE_FTGLYPH_H +#include <freetype/ftglyph.h> +#endif +#ifdef HAVE_TTTABLES_H +#include <freetype/tttables.h> +#endif +#ifdef HAVE_FTNAMES_H +#include <freetype/ftnames.h> +#endif +#ifdef HAVE_FTSNAMES_H +#include <freetype/ftsnames.h> +#endif +#ifdef HAVE_TTNAMEID_H +#include <freetype/ttnameid.h> +#endif + #include <sys/types.h> #include <dirent.h> #include <string.h> diff -urN ../wine-20010529cvs/include/acconfig.h ./include/acconfig.h --- ../wine-20010529cvs/include/acconfig.h Tue May 29 18:16:35 2001 +++ ./include/acconfig.h Thu May 31 09:17:56 2001 @@ -129,3 +129,11 @@ /* Define if FreeType 2 is installed */ #undef HAVE_FREETYPE + +/* Define if various FreeType headers are present */ +#undef HAVE_FREETYPE_H +#undef HAVE_FTGLYPH_H +#undef HAVE_TTTABLES_H +#undef HAVE_FTNAMES_H +#undef HAVE_FTSNAMES_H +#undef HAVE_TTNAMEID_H

2 1

[Fwd: autoconf help needed [was wineps include fix.]]
by Ian Pilcher May 31, 2001

May 31, 2001

Ian Pilcher wrote: > > Marcus Meissner wrote: > > > > Add here: > > > > CFLAGS="$CFLAGS -I$ft_incl_dir" > > > > Works great. Thanks! > I spoke too soon. It's finding /usr/include/freetype/freetype.h (from FreeType 1.x). The test is not paying any attention to the CFLAGS variable. So how does one get the autoconf tests to look in a non-standard directory for header files? -- ======================================================================== Ian Pilcher ian.pilcher(a)home.com ========================================================================

1 0

Re: WINE server messages
by Alexandre Julliard May 31, 2001

May 31, 2001

David Howells <dhowells(a)redhat.com> writes: > I'm having a little trouble deciding exactly how to emulate the "module > registration" functionality in my kernel module. It occurs to me that this > might be easier to accomplish with a change to the current wine server message > set. My idea is: > > * Have the server only deal with NT Section objects and views of Sections. > > * Have no separate module table attached to a process. > > * Implement NtQuerySectionInformation/NtSetSectionInformation calls (or > whatever they're called) as wineserver messages. > > * Add an extra Wine-specific information class for the purpose of recording > the extra module information. > > * The wineserver process structure can then be changed so that rather than > keeping a separate list of process_dlls, they can just keep a list of > section views, some of which will be images/modules. Maintaining a section list in the server is certainly something we could do, but I don't really see why you want to get rid of the modules list. What would you gain by doing that?> -- Alexandre Julliard julliard(a)winehq.com

2 1

PathGetCharType/PathGetCharTypeA
by Dax Kelson May 31, 2001

May 31, 2001

I'm having a failure with a windows app. The application starts, and it asks me to name my project and pick a directory to store it in. When I do so, I get errors such as: fixme:shell:PathGetCharTypeA d fixme:shell:PathGetCharTypeA f fixme:shell:PathGetCharTypeA d fixme:shell:PathGetCharTypeA t And apps reports "such such character isn't valid", and doesn't continue (each time I try again, it generates another fixme message). According to MSDN: http://msdn.microsoft.com/library/psdk/shellcc/shell/SHLWAPI/Path/PathGetCh… PathGetCharType/PathGetCharTypeA part of shlwapi.h returns one or more of the following values that define the type of character: GCT_INVALID The character is not valid in a path. GCT_LFNCHAR The character is valid in a long file name. GCT_SEPARATOR The character is a path separator. GCT_SHORTCHAR The character is valid in a short (8.3) file name. GCT_WILD The character is a wildcard character. This is the current Wine code: /************************************************************************* * PathGetCharTypeA [SHLWAPI.@] */ UINT WINAPI PathGetCharTypeA(UCHAR ch) { FIXME("%c\n", ch); return 0; } I'm a perl guy, but I'm learning C. Maybe I'm naive, but fleshing out the Wine version of this function shouldn't be too hard it seems. You'd have to go track down the rules. Can some point me in the right direction on fixing this up? Can someone give me a quick hack to make my application work? Many thanks, Dax

2 3

autoconf help needed [was wineps include fix.]
by Ian Pilcher May 31, 2001

May 31, 2001

Alexandre Julliard wrote: > > Basically do a > > AC_CHECK_HEADERS(freetype/freetype.h freetype/foo.h freetype/bar.h) > Unfortunately it's not that simple, because the FreeType include files won't always be in /usr/include/freetype. On Red Hat 7.1, for example, they're in /usr/include/freetype2/freetype, to distinguish them from the FreeType 1.x headers. The required compiler flag to include the proper directories is in the FREETYPEINCL variable. For example, on my Red Hat system it is set to '-I/usr/include/freetype2'. I tried the following: ft_incl_dir=${FREETYPEINCL#-I} AC_CHECK_HEADER("$ft_incl_dir/freetype/freetype.h",AC_DEFINE(HAVE_FREETYPE_H)) When I run autoconf, autoheader, and configure, I get the following: checking for FT_Init_FreeType in -lfreetype... yes checking for freetype-config... freetype-config checking for /usr/include/freetype2/freetype/freetype.h... no So the AC_CHECK_HEADER macro isn't finding the file, even though it is right there. Anyone have any idea why? -- ======================================================================== Ian Pilcher ian.pilcher(a)home.com ========================================================================

2 1

Re: wineps include fix.
by Alexandre Julliard May 31, 2001

May 31, 2001

Ian Pilcher <ian.pilcher(a)home.com> writes: > Did you read somewhere that they're getting rid of freetype.h? > > I've looked at 2.0.1 and 2.0.2: > > * In 2.0.1, the header macros are defined in > freetype/config/ftbuild.h, which is included in freetype/freetype.h. > > * In 2.0.2, the header macros are defined in ft2build.h, which is > included in freetype/freetype.h. > > So as long as they keep freetype/freetype.h around, we can include that > and get the macro definitions. The page at http://freetype.sourceforge.net/freetype2/docs/tutorial/step1.html says that you have to include ft2build.h and use macros to include freetype.h, and that other inclusion schemes will get broken in 2.1. I have no idea if this page is up-to-date or if the recommendations have changed again. > We still have to test which macros are defined and only include the ones > that exist, but it does save the work of adding extra autoconf checks. Except with the autoconf checks we control what macros are being defined, we don't have to guess which file to include to get the proper macros. Frankly this idea of defining macros to specify include file names is hopelessly brain-damaged, and the less we have to do with that the happier I will be. -- Alexandre Julliard julliard(a)winehq.com

2 1

Re: PATCH: Version 2, GetX11WindowId
by Alexandre Julliard May 30, 2001

May 30, 2001

Nikolas Zimmermann <wildfox(a)kde.org> writes: > ah > i mean, this feature would _only_ be used in kdenonbeta/activexproxy > and it would be great to have this in CVS until you've done this rewrite-task. > > Do you think that's a good, short-term, solution for me? For you certainly. But it doesn't have to be in CVS for you to use it, does it? These kinds of quick hacks have a way of staying around much too long, especially when external packages depend on them, and the best way to avoid that is to not put them in CVS the first place. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: wineps include fix.
by Alexandre Julliard May 30, 2001

May 30, 2001

Ian Pilcher <ian.pilcher(a)home.com> writes: > I *believe* that <freetype/freetype.h> should always include the header > that defines the macros. If not, it's going to be a nightmare checking > for 2.0.1, 2.0.2, 2.0.3, etc. -- let alone every intermediate snapshot > that a rawhide/cooker distribution might use. It seems the rule is now to use ft2build.h instead of freetype.h. And this will certainly change in the next release again... so yes, it will be a nightmare if we actually try to use the silly macros. But if we simply bypass them and do autoconf checks like we do for every other package, I think it should work, and be harder to break (though I'm sure the freetype guys will manage to do it ;-) Basically do a AC_CHECK_HEADERS(freetype/freetype.h freetype/foo.h freetype/bar.h) and then #ifdef HAVE_FREETYPE_FREETYPE_H #include <freetype/freetype.h> #endif #ifdef HAVE_FREETYPE_FOO_H #include <freetype/foo.h> #endif etc. Then when they change all the header names again in the next release we can simply add the new names to the list. -- Alexandre Julliard julliard(a)winehq.com

2 1