winetest experience
Okay, so I boldly tried to use winetest with what documentation I could find, and had an...um...interesting time. I created these files: [jertop] cat build.id fcccd9fca605d1d4c462df5c33f4bacf03bdda5f [jertop] cat build.nfo A Large Shovel [jertop] cat tests.url http://www.IDontKnowWhatURLToPutHere.com/ [jertop] did a make dist, and then did: ./winetest -c -t "jw-etch32" It ran, did it's thing, and had one interactive thing (Gecko fussed at me; that's not a Winetest bug afaik). Then when it was all done, it transferred my nearly 1 MB file, and then errored out with: "Unknown build id" So then I looked at the output file, and sure enough, it had a - for build info, not my fancy git id. So I hacked that, put in jwtip, and then ran winetest -s to send my output file through. And then I have a lovely result here: http://test.winehq.org/data/jwtip/ So that's *something* at least. Although I suspect someone will now have to go clean up my mess :-/. So...what's the convention for build.id etc? And why didn't they get set? Cheers, Jeremy
Re: War on conformance test suite failures!
On Monday 04 February 2008 04:06:10 pm Stefan Dösinger wrote: > The bit that interests me is the sRGB test result. It shows that the sRGB > correction is applied after the fog, which would allow us to use > GLX_EXT_framebuffer_sRGB for performance improvements if we can find out in > which cases games have to expect that. Currently I only know that Half Life > 2 should fail on this system. This might be the reason: http://msdn2.microsoft.com/en-us/library/bb172583(VS.85).aspx D3DPMISCCAPS_POSTBLENDSRGBCONVERT - Device supports conversion to sRGB after blending. This flag is available in Direct3D 9Ex only.
Re: War on conformance test suite failures!
> What's the best way to encourage people to fix these problems? > Should we designate some upcoming day, week, or month > as a conformance test bug squishing party? > Should we offer prizes (or at least notoriety) for > the person who does the best job fixing > conformance test suite bugs (as judged by Alexandre > or his designate)? > Or is a simple call to arms enough? I was struck at how willing people were to work on it at Wineconf; I suspect that a call to arms will do it, so long as someone sticks around to pay attention to the results. Of course, the WPF is relatively flush, so we could offer some prizes as well... I was hoping to sound a cry for the use of winetest [1], but was stymied by a lack of documentation around winetest. Cheers, Jeremy [1] http://www.winehq.org/pipermail/wine-devel/2007-October/059846.html
Re: War on conformance test suite failures!
Am Dienstag, 5. Februar 2008 00:50:55 schrieb Dan Kegel: > Great progress was made at Wineconf last year on > getting our test suite closer to always passing on wine, but > http://test.winehq.org/data/200801301937/#Wine shows > that, according to the results collected from people who run > programs/winetest on Wine, twelve DLLs' tests are currently failing. > (Let alone the test failures on Windows!) > http://bugs.winehq.org/show_bug.cgi?id=9916 also > talks about the fact that "make test" shows failures. This is only half on-topic, but the d3d9:visual test ran on this machine has some interesting results: Vista: Vista-HomePrem-NoUAC Do we have any track who reported them? The bit that interests me is the sRGB test result. It shows that the sRGB correction is applied after the fog, which would allow us to use GLX_EXT_framebuffer_sRGB for performance improvements if we can find out in which cases games have to expect that. Currently I only know that Half Life 2 should fail on this system.
War on conformance test suite failures!
Great progress was made at Wineconf last year on getting our test suite closer to always passing on wine, but http://test.winehq.org/data/200801301937/#Wine shows that, according to the results collected from people who run programs/winetest on Wine, twelve DLLs' tests are currently failing. (Let alone the test failures on Windows!) http://bugs.winehq.org/show_bug.cgi?id=9916 also talks about the fact that "make test" shows failures. This situation greatly confuses new developers, who assume that any test failure is somehow their fault. And that's a reasonable assumption, let's make it so! It would make validating a new Wine development environment easy -- it'd be great to be able to say If it doesn't pass "make test" with no errors, something's wrong with the build environment. What's the best way to encourage people to fix these problems? Should we designate some upcoming day, week, or month as a conformance test bug squishing party? Should we offer prizes (or at least notoriety) for the person who does the best job fixing conformance test suite bugs (as judged by Alexandre or his designate)? Or is a simple call to arms enough?
Re: running "make test" results in an error
Am Montag, 4. Februar 2008 18:41:23 schrieb Christopher: > err:xrandr:X11DRV_XRandR_SetCurrentMode Resolution change not successful -- > perhaps display has changed? device.c:753: Test failed: Screen width is > 1680 > device.c:754: Test failed: Screen height is 1050 That is causing the tests to fail. I've never seen that specific behavior before, but I think that winex11 doesn't return an error if the resolution change fails. This is because some users have "broken" X11 setups which only support one resolution. That way games run in a corner of the screen instead of bailing out. The consequence is that the test isn't told that the resolution switch failed, and then complains about an unexpected resolution. I think the problem with the test is that it assumes that 640x480 is available. I haven't seen a Windows box yet where this wasn't the case, but I think the best option is to check for that and skip the test with a warning to avoid failing make test. Obviously, games that require 640x480 will have issues on your computer as well.
Re: [Fwd: d3dx8: Implement D3DXCreateTextureFromFile]
Why has this patch not been accepted? Luis C. Busquets Pérez escribió: > I have created a /dlls/d3dx8/texture.c file where to put all functions > related to textures and d3dx8. > > I have included D3DXIMAGE_FILEFORMAT in the patch because it is > referred by D3DXIMAGE_FILEFORMAT which is referred in the function. If > not included, it would not compile. They both are now in > /include/d3dx8.h whci I think is the appropiate file. Do you propose > to put them elsewhere? > > Do you think I am missing anything or is it ok?
Re: running "make test" results in an error
On Feb 4, 2008 1:31 PM, Dan Kegel <[EMAIL PROTECTED]> wrote: > Christopher raccoonone at procyongames.com wrote: > >I tried running "make test" under Ubuntu 7.10, and I just updated to the > >latest cvs this morning so it's not too old. However, after only running > >a couple of tests it exited with an error. Is this normal > > Sadly, yes. See http://bugs.winehq.org/show_bug.cgi?id=9916 > > Believe it or not, the situation was much worse five months ago. > At the last Wineconf, Jeremy White got everybody to spend > a whole day just fixing test failures. We could use something > like that again. +1 -Austin
Re: winedbg pdb issue - n00b
Michel Jacques a écrit : > Hi. > > I've have setup my debug build (with pdbs) and MSVCRT debug dlls. > > When stopping on a breakpoint with winedbg, I get a stack of calls in winedbg > which does not > contains any function info from my dlls or app. I only get hex offset of > call within my dll. But > I do see the information for wine sources though, function name + line number. > > What do I need to do so that winedbg can extract info from my pdb? > _NT_SYMBOL_PATH env variable should point to where your pdb files are A+ -- Eric Pouech "The problem with designing something completely foolproof is to underestimate the ingenuity of a complete idiot." (Douglas Adams)
re: running "make test" results in an error
Christopher raccoonone at procyongames.com wrote: >I tried running "make test" under Ubuntu 7.10, and I just updated to the >latest cvs this morning so it's not too old. However, after only running >a couple of tests it exited with an error. Is this normal Sadly, yes. See http://bugs.winehq.org/show_bug.cgi?id=9916 Believe it or not, the situation was much worse five months ago. At the last Wineconf, Jeremy White got everybody to spend a whole day just fixing test failures. We could use something like that again. > and if so how do I run the rest of the tests? Elementary, my dear Watson. "make -k test". - Dan
winedbg pdb issue - n00b
Hi. I've have setup my debug build (with pdbs) and MSVCRT debug dlls. When stopping on a breakpoint with winedbg, I get a stack of calls in winedbg which does not contains any function info from my dlls or app. I only get hex offset of call within my dll. But I do see the information for wine sources though, function name + line number. What do I need to do so that winedbg can extract info from my pdb? Thanks, Michel Découvrez les styles qui font sensation sur Yahoo! Québec Avatars. http://cf.avatars.yahoo.com/
running "make test" results in an error
I tried running "make test" under Ubuntu 7.10, and I just updated to the latest cvs this morning so it's not too old. However, after only running a couple of tests it exited with an error. Is this normal, and if so how do I run the rest of the tests? I attached a log showing which test fails. Christopher make[1]: Entering directory `/home/christopher/wine-git/tools' make[1]: `makedep' is up to date. make[1]: Leaving directory `/home/christopher/wine-git/tools' make[1]: Entering directory `/home/christopher/wine-git/dlls' make[2]: Entering directory `/home/christopher/wine-git/dlls/advapi32/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/advapi32/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/advpack/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/advpack/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/browseui/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/browseui/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/cabinet/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/cabinet/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/comcat/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/comcat/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/comctl32/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/comctl32/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/comdlg32/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/comdlg32/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/credui/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/credui/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/crypt32/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/crypt32/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/cryptnet/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/cryptnet/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/d3d8/tests' make[2]: Nothing to be done for `test'. make[2]: Leaving directory `/home/christopher/wine-git/dlls/d3d8/tests' make[2]: Entering directory `/home/christopher/wine-git/dlls/d3d9/tests' ../../../tools/runtest -q -P wine -M d3d9.dll -T ../../.. -p d3d9_test.exe.so device.c && touch device.ok fixme:win:EnumDisplayDevicesW ((null),0,0x34f8c0,0x), stub! fixme:d3d:IWineD3DDeviceImpl_CreateAdditionalSwapChain The app requests more than one back buffer, this can't be supported properly. Please configure the application to use double buffering(=1 back buffer) if possible err:xrandr:X11DRV_XRandR_SetCurrentMode Resolution change not successful -- perhaps display has changed? device.c:753: Test failed: Screen width is 1680 device.c:754: Test failed: Screen height is 1050 err:xrandr:X11DRV_XRandR_SetCurrentMode Resolution change not successful -- perhaps display has changed? device.c:798: Test failed: Screen width is 1680 device.c:799: Test failed: Screen height is 1050 err:d3d:IWineD3DDeviceImpl_DrawIndexedPrimitive (0x144548) : Called without a valid index buffer set, returning WINED3DERR_INVALIDCALL fixme:d3d:SetupForBlit > GL_INVALID_VALUE (0x501) from glOrtho @ context.c / 622 fixme:d3d_surface:flush_to_framebuffer_drawpixels > GL_INVALID_VALUE (0x501) from glDrawPixels @ surface.c / 1061 fixme:d3d:transform_projection > GL_INVALID_VALUE (0x501) from glOrtho @ state.c / 2802 fixme:d3d_surface:flush_to_framebuffer_drawpixels > GL_INVALID_VALUE (0x501) from glDrawPixels @ surface.c / 1061 fixme:d3d:IWineD3DDeviceImpl_SetLightEnable Too many concurrently active lights make[2]: *** [device.ok] Error 4 make[2]: Leaving directory `/home/christopher/wine-git/dlls/d3d9/tests' make[1]: *** [d3d9/tests/__test__] Error 2 make[1]: Leaving directory `/home/christopher/wine-git/dlls' make: *** [dlls/__test__] Error 2
Re: winehq.org down?
WineHQ.org, AppDB, and Bugzilla are all on the same server. We have been having some issues with mysqld crashing the entire server. It so far has been a hard issue to track down. I've been tweaking the mysql config settings to hopefully prevent this issue. James McKenzie wrote: > Austin English wrote: >> On Feb 3, 2008 3:32 PM, Reece Dunn <[EMAIL PROTECTED]> wrote: >> >>> On 03/02/2008, James Hawkins <[EMAIL PROTECTED]> wrote: >>> Hey guys, I'm having problems connecting to the winehq.org server. Is this a known issue? >>> It's working my side. Is there a problem with your connection? Do >>> other sites work? >>> >>> - Reece >>> >>> >> It's off and on...Seems to be up right now (and has been for a couple >> hours), but earlier today was out. >> >> > And bugs.winehq.org seemed to have crashed last night around 200 GMT. > Of course, the problem may have been me. > > James McKenzie > >
Re: attempt to install Wine from source
By the way, 20050803 seems to be a very old source package.
Chris Spencer <[EMAIL PROTECTED]> a écrit : You do not have the gcc compiler
installed. On Ubuntu you will need to
install build-essentials (I think that's what it's called), and also run
'sudo apt-get build-dep wine'. I'm not sure what the process is on Debian.
Mike Harrison wrote:
> Dear Sir;
> This below is the config.log I got from trying to install Wine (a source
> archive from a British Linux mag) on to my AMD64 m/c under Debian 4.0.
> 64 bit OS.
> A similar message was obtained from an attempt to install Wine on my
> AMD64 laptop under Ubuntu 7.04. (not 64 bit).
> From the report log I can't identify just what went wrong.
> My aim is to use Wine to run Windows XP applications on both machines,
> and if possible Windows Vista applic'ns on the laptop - both machines
> running 32 bit applic'ns. My first priority for this is MS Excel XP pro.
>
> From a brief visit to WineHQ today (the connection died for some
> unknown reason) I believe it may not be as straightforward a project as
> I had hoped. Please tell me either what I must do to load/install my
> Wine source package, or where I have to go for help to go a little further.
> I prefer to load the sources I already have, plus supplementary
> programs, if that's possible.
> Any advice you can give would be appreciated.
> Thanks;
> Mike Harrison
>
>
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
>
> It was created by Wine configure 20050830, which was
> generated by GNU Autoconf 2.59. Invocation command line was
>
> $ ./configure -C --prefix=/usr/local
>
> ## - ##
> ## Platform. ##
> ## - ##
>
> hostname = ultima
> uname -m = x86_64
> uname -r = 2.6.18-4-amd64
> uname -s = Linux
> uname -v = #1 SMP Mon Mar 26 11:36:53 CEST 2007
>
> /usr/bin/uname -p = unknown
> /bin/uname -X = unknown
>
> /bin/arch = x86_64
> /usr/bin/arch -k = unknown
> /usr/convex/getsysinfo = unknown
> hostinfo = unknown
> /bin/machine = unknown
> /usr/bin/oslevel = unknown
> /bin/universe = unknown
>
> PATH: /usr/local/bin
> PATH: /usr/bin
> PATH: /bin
> PATH: /usr/bin/X11
> PATH: /usr/games
>
>
> ## --- ##
> ## Core tests. ##
> ## --- ##
>
> configure:1249: creating cache config.cache
> configure:1424: checking build system type
> configure:1442: result: x86_64-unknown-linux-gnu
> configure:1450: checking host system type
> configure:1464: result: x86_64-unknown-linux-gnu
> configure:1504: checking whether make sets $(MAKE)
> configure:1524: result: yes
> configure:1579: checking for gcc
> configure:1605: result: gcc -m32
> configure:1849: checking for C compiler version
> configure:1852: gcc -m32 --version &5
> ./configure: line 1853: gcc: command not found
> configure:1855: $? = 127
> configure:1857: gcc -m32 -v &5
> ./configure: line 1858: gcc: command not found
> configure:1860: $? = 127
> configure:1862: gcc -m32 -V &5
> ./configure: line 1863: gcc: command not found
> configure:1865: $? = 127
> configure:1888: checking for C compiler default output file name
> configure:1891: gcc -m32conftest.c >&5
> ./configure: line 1892: gcc: command not found
> configure:1894: $? = 127
> configure: failed program was:
> | /* confdefs.h. */
> |
> | #define PACKAGE_NAME "Wine"
> | #define PACKAGE_TARNAME "wine"
> | #define PACKAGE_VERSION "20050830"
> | #define PACKAGE_STRING "Wine 20050830"
> | #define PACKAGE_BUGREPORT "wine-devel@winehq.org"
> | /* end confdefs.h. */
> |
> | int
> | main ()
> | {
> |
> | ;
> | return 0;
> | }
> configure:1933: error: C compiler cannot create executables
> See `config.log' for more details.
>
> ## ##
> ## Cache variables. ##
> ## ##
>
> ac_cv_build=x86_64-unknown-linux-gnu
> ac_cv_build_alias=x86_64-unknown-linux-gnu
> ac_cv_env_CC_set=
> ac_cv_env_CC_value=
> ac_cv_env_CFLAGS_set=
> ac_cv_env_CFLAGS_value=
> ac_cv_env_CPPFLAGS_set=
> ac_cv_env_CPPFLAGS_value=
> ac_cv_env_CPP_set=
> ac_cv_env_CPP_value=
> ac_cv_env_CXXFLAGS_set=
> ac_cv_env_CXXFLAGS_value=
> ac_cv_env_CXX_set=
> ac_cv_env_CXX_value=
> ac_cv_env_LDFLAGS_set=
> ac_cv_env_LDFLAGS_value=
> ac_cv_env_build_alias_set=
> ac_cv_env_build_alias_value=
> ac_cv_env_host_alias_set=
> ac_cv_env_host_alias_value=
> ac_cv_env_target_alias_set=
> ac_cv_env_target_alias_value=
> ac_cv_host=x86_64-unknown-linux-gnu
> ac_cv_host_alias=x86_64-unknown-linux-gnu
> ac_cv_prog_ac_ct_CC='gcc -m32'
> ac_cv_prog_make_make_set=yes
>
> ## - ##
> ## Output variables. ##
> ## - ##
>
> ALSALIBS=''
> AR=''
> ARTSCCONFIG=''
> ARTSINCL=''
> ARTSLIBS=''
> AS='as --32'
> AUDIOIOLIBS=''
> BISON=''
> BUILTINFLAG=''
> CC='gcc -m32'
> CFLAGS=''
> COREFOUNDATIONLIB=''
> CPP=''
> CPPBIN=''
> CPPFLAGS=''
> CROSSCC=''
> CROSSTEST=''
> CROSSWINDRES=''
> CRTLIBS=''
> CURSESLIBS=''
> CXX=''
>
Re: attempt to install Wine from source
You do not have the gcc compiler installed. On Ubuntu you will need to
install build-essentials (I think that's what it's called), and also run
'sudo apt-get build-dep wine'. I'm not sure what the process is on Debian.
Mike Harrison wrote:
> Dear Sir;
> This below is the config.log I got from trying to install Wine (a source
> archive from a British Linux mag) on to my AMD64 m/c under Debian 4.0.
> 64 bit OS.
> A similar message was obtained from an attempt to install Wine on my
> AMD64 laptop under Ubuntu 7.04. (not 64 bit).
> From the report log I can't identify just what went wrong.
> My aim is to use Wine to run Windows XP applications on both machines,
> and if possible Windows Vista applic'ns on the laptop - both machines
> running 32 bit applic'ns. My first priority for this is MS Excel XP pro.
>
> From a brief visit to WineHQ today (the connection died for some
> unknown reason) I believe it may not be as straightforward a project as
> I had hoped. Please tell me either what I must do to load/install my
> Wine source package, or where I have to go for help to go a little further.
> I prefer to load the sources I already have, plus supplementary
> programs, if that's possible.
> Any advice you can give would be appreciated.
> Thanks;
> Mike Harrison
>
>
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
>
> It was created by Wine configure 20050830, which was
> generated by GNU Autoconf 2.59. Invocation command line was
>
> $ ./configure -C --prefix=/usr/local
>
> ## - ##
> ## Platform. ##
> ## - ##
>
> hostname = ultima
> uname -m = x86_64
> uname -r = 2.6.18-4-amd64
> uname -s = Linux
> uname -v = #1 SMP Mon Mar 26 11:36:53 CEST 2007
>
> /usr/bin/uname -p = unknown
> /bin/uname -X = unknown
>
> /bin/arch = x86_64
> /usr/bin/arch -k = unknown
> /usr/convex/getsysinfo = unknown
> hostinfo = unknown
> /bin/machine = unknown
> /usr/bin/oslevel = unknown
> /bin/universe = unknown
>
> PATH: /usr/local/bin
> PATH: /usr/bin
> PATH: /bin
> PATH: /usr/bin/X11
> PATH: /usr/games
>
>
> ## --- ##
> ## Core tests. ##
> ## --- ##
>
> configure:1249: creating cache config.cache
> configure:1424: checking build system type
> configure:1442: result: x86_64-unknown-linux-gnu
> configure:1450: checking host system type
> configure:1464: result: x86_64-unknown-linux-gnu
> configure:1504: checking whether make sets $(MAKE)
> configure:1524: result: yes
> configure:1579: checking for gcc
> configure:1605: result: gcc -m32
> configure:1849: checking for C compiler version
> configure:1852: gcc -m32 --version &5
> ./configure: line 1853: gcc: command not found
> configure:1855: $? = 127
> configure:1857: gcc -m32 -v &5
> ./configure: line 1858: gcc: command not found
> configure:1860: $? = 127
> configure:1862: gcc -m32 -V &5
> ./configure: line 1863: gcc: command not found
> configure:1865: $? = 127
> configure:1888: checking for C compiler default output file name
> configure:1891: gcc -m32conftest.c >&5
> ./configure: line 1892: gcc: command not found
> configure:1894: $? = 127
> configure: failed program was:
> | /* confdefs.h. */
> |
> | #define PACKAGE_NAME "Wine"
> | #define PACKAGE_TARNAME "wine"
> | #define PACKAGE_VERSION "20050830"
> | #define PACKAGE_STRING "Wine 20050830"
> | #define PACKAGE_BUGREPORT "wine-devel@winehq.org"
> | /* end confdefs.h. */
> |
> | int
> | main ()
> | {
> |
> | ;
> | return 0;
> | }
> configure:1933: error: C compiler cannot create executables
> See `config.log' for more details.
>
> ## ##
> ## Cache variables. ##
> ## ##
>
> ac_cv_build=x86_64-unknown-linux-gnu
> ac_cv_build_alias=x86_64-unknown-linux-gnu
> ac_cv_env_CC_set=
> ac_cv_env_CC_value=
> ac_cv_env_CFLAGS_set=
> ac_cv_env_CFLAGS_value=
> ac_cv_env_CPPFLAGS_set=
> ac_cv_env_CPPFLAGS_value=
> ac_cv_env_CPP_set=
> ac_cv_env_CPP_value=
> ac_cv_env_CXXFLAGS_set=
> ac_cv_env_CXXFLAGS_value=
> ac_cv_env_CXX_set=
> ac_cv_env_CXX_value=
> ac_cv_env_LDFLAGS_set=
> ac_cv_env_LDFLAGS_value=
> ac_cv_env_build_alias_set=
> ac_cv_env_build_alias_value=
> ac_cv_env_host_alias_set=
> ac_cv_env_host_alias_value=
> ac_cv_env_target_alias_set=
> ac_cv_env_target_alias_value=
> ac_cv_host=x86_64-unknown-linux-gnu
> ac_cv_host_alias=x86_64-unknown-linux-gnu
> ac_cv_prog_ac_ct_CC='gcc -m32'
> ac_cv_prog_make_make_set=yes
>
> ## - ##
> ## Output variables. ##
> ## - ##
>
> ALSALIBS=''
> AR=''
> ARTSCCONFIG=''
> ARTSINCL=''
> ARTSLIBS=''
> AS='as --32'
> AUDIOIOLIBS=''
> BISON=''
> BUILTINFLAG=''
> CC='gcc -m32'
> CFLAGS=''
> COREFOUNDATIONLIB=''
> CPP=''
> CPPBIN=''
> CPPFLAGS=''
> CROSSCC=''
> CROSSTEST=''
> CROSSWINDRES=''
> CRTLIBS=''
> CURSESLIBS=''
> CXX=''
> CXXFLAGS=''
> DEFS=''
> DLLDEFS=''
> DLLEXT=''
> DLLFLAGS=''
> DLLIBS=''
> DLLTOOL=''
> DLLWRAP=''
> ECHO_
Re: winehq.org down?
Austin English wrote: > On Feb 3, 2008 3:32 PM, Reece Dunn <[EMAIL PROTECTED]> wrote: > >> On 03/02/2008, James Hawkins <[EMAIL PROTECTED]> wrote: >> >>> Hey guys, >>> >>> I'm having problems connecting to the winehq.org server. Is this a known >>> issue? >>> >> It's working my side. Is there a problem with your connection? Do >> other sites work? >> >> - Reece >> >> > > It's off and on...Seems to be up right now (and has been for a couple > hours), but earlier today was out. > > And bugs.winehq.org seemed to have crashed last night around 200 GMT. Of course, the problem may have been me. James McKenzie
Re: winehq.org down?
On Feb 3, 2008 3:32 PM, Reece Dunn <[EMAIL PROTECTED]> wrote: > On 03/02/2008, James Hawkins <[EMAIL PROTECTED]> wrote: > > Hey guys, > > > > I'm having problems connecting to the winehq.org server. Is this a known > > issue? > > It's working my side. Is there a problem with your connection? Do > other sites work? > > - Reece > It's off and on...Seems to be up right now (and has been for a couple hours), but earlier today was out. -Austin
attempt to install Wine from source
Dear Sir;
This below is the config.log I got from trying to install Wine (a source
archive from a British Linux mag) on to my AMD64 m/c under Debian 4.0.
64 bit OS.
A similar message was obtained from an attempt to install Wine on my
AMD64 laptop under Ubuntu 7.04. (not 64 bit).
From the report log I can't identify just what went wrong.
My aim is to use Wine to run Windows XP applications on both machines,
and if possible Windows Vista applic'ns on the laptop - both machines
running 32 bit applic'ns. My first priority for this is MS Excel XP pro.
From a brief visit to WineHQ today (the connection died for some
unknown reason) I believe it may not be as straightforward a project as
I had hoped. Please tell me either what I must do to load/install my
Wine source package, or where I have to go for help to go a little further.
I prefer to load the sources I already have, plus supplementary
programs, if that's possible.
Any advice you can give would be appreciated.
Thanks;
Mike Harrison
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by Wine configure 20050830, which was
generated by GNU Autoconf 2.59. Invocation command line was
$ ./configure -C --prefix=/usr/local
## - ##
## Platform. ##
## - ##
hostname = ultima
uname -m = x86_64
uname -r = 2.6.18-4-amd64
uname -s = Linux
uname -v = #1 SMP Mon Mar 26 11:36:53 CEST 2007
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = x86_64
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/local/bin
PATH: /usr/bin
PATH: /bin
PATH: /usr/bin/X11
PATH: /usr/games
## --- ##
## Core tests. ##
## --- ##
configure:1249: creating cache config.cache
configure:1424: checking build system type
configure:1442: result: x86_64-unknown-linux-gnu
configure:1450: checking host system type
configure:1464: result: x86_64-unknown-linux-gnu
configure:1504: checking whether make sets $(MAKE)
configure:1524: result: yes
configure:1579: checking for gcc
configure:1605: result: gcc -m32
configure:1849: checking for C compiler version
configure:1852: gcc -m32 --version &5
./configure: line 1853: gcc: command not found
configure:1855: $? = 127
configure:1857: gcc -m32 -v &5
./configure: line 1858: gcc: command not found
configure:1860: $? = 127
configure:1862: gcc -m32 -V &5
./configure: line 1863: gcc: command not found
configure:1865: $? = 127
configure:1888: checking for C compiler default output file name
configure:1891: gcc -m32conftest.c >&5
./configure: line 1892: gcc: command not found
configure:1894: $? = 127
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME "Wine"
| #define PACKAGE_TARNAME "wine"
| #define PACKAGE_VERSION "20050830"
| #define PACKAGE_STRING "Wine 20050830"
| #define PACKAGE_BUGREPORT "wine-devel@winehq.org"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:1933: error: C compiler cannot create executables
See `config.log' for more details.
## ##
## Cache variables. ##
## ##
ac_cv_build=x86_64-unknown-linux-gnu
ac_cv_build_alias=x86_64-unknown-linux-gnu
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXFLAGS_set=
ac_cv_env_CXXFLAGS_value=
ac_cv_env_CXX_set=
ac_cv_env_CXX_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_host=x86_64-unknown-linux-gnu
ac_cv_host_alias=x86_64-unknown-linux-gnu
ac_cv_prog_ac_ct_CC='gcc -m32'
ac_cv_prog_make_make_set=yes
## - ##
## Output variables. ##
## - ##
ALSALIBS=''
AR=''
ARTSCCONFIG=''
ARTSINCL=''
ARTSLIBS=''
AS='as --32'
AUDIOIOLIBS=''
BISON=''
BUILTINFLAG=''
CC='gcc -m32'
CFLAGS=''
COREFOUNDATIONLIB=''
CPP=''
CPPBIN=''
CPPFLAGS=''
CROSSCC=''
CROSSTEST=''
CROSSWINDRES=''
CRTLIBS=''
CURSESLIBS=''
CXX=''
CXXFLAGS=''
DEFS=''
DLLDEFS=''
DLLEXT=''
DLLFLAGS=''
DLLIBS=''
DLLTOOL=''
DLLWRAP=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
ESDCONFIG=''
ESDINCL=''
ESDLIBS=''
EXEEXT=''
EXTRACFLAGS=''
FONTFORGE=''
FONTSSUBDIRS=''
FREETYPEINCL=''
FREETYPELIBS=''
GLU32FILES=''
GLUT32FILES=''
GLUT_LIBS=''
ICULIBS=''
IMPLIBEXT=''
INSTALL_DATA=''
INSTALL_PROGRAM=''
INSTALL_SCRIPT=''
IOKITLIB=''
LCMSLIBS=''
LD='ld -m elf_i386'
LDAPLIBS=''
LDCONFIG=''
LDD=''
LDDLLFLAGS=''
LDEXECFLAGS=''
LDFLAGS=''
LDLIBWINEFLAGS=''
LDPATH=''
LDSHARED=''
LEX=''
LEXLIB=''
LEX_OUTPUT_ROOT=''
LIBEXT=''
LIBOBJS=''
LIBPTHREAD=''
LIBS=''
LINT=''
LINTFLAGS=''
LN=''
LN_S=''
LTLIBOBJS=''
MAIN_BINARY=''
NASLIBS=
Re: winehq.org down?
On 03/02/2008, James Hawkins <[EMAIL PROTECTED]> wrote: > Hey guys, > > I'm having problems connecting to the winehq.org server. Is this a known > issue? It's working my side. Is there a problem with your connection? Do other sites work? - Reece
