Hi Alexandre,
Was this dropped? On my laptop (a 600mhz Pentium with 128mb of ram, so not too pokey) attempting to build the winetest binary actually kills the build dead. It ends up attempting to feed ~20mb of data to gas which doesn't make it very happy. I guess I misphrased it - it's not for slower machines, it's for machines with less memory.
There's not much reason to run the entire winetest binary on Wine itself, so why do we always build it ?
thanks -mike
Mike Hearn <mike_at_navi.cx> Don't compile winetest as part of the main build to avoid problems on low memory machines.
--- programs/winetest/Makefile.in.~1.30.~ 2004-07-22 20:43:42.000000000 +0100 +++ programs/winetest/Makefile.in 2004-08-01 23:44:24.334453984 +0100 @@ -1,3 +1,7 @@ +# MKPROG_SKIP
+# This program must be built explicitly to make compiles on slower machines easier
TOPSRCDIR = @top_srcdir@ TOPOBJDIR = ../.. SRCDIR = @srcdir@
Mike Hearn m.hearn@signal.qinetiq.com writes:
Was this dropped? On my laptop (a 600mhz Pentium with 128mb of ram, so not too pokey) attempting to build the winetest binary actually kills the build dead. It ends up attempting to feed ~20mb of data to gas which doesn't make it very happy. I guess I misphrased it - it's not for slower machines, it's for machines with less memory.
There's not much reason to run the entire winetest binary on Wine itself, so why do we always build it ?
Because code that doesn't get built rots very quickly. You can disable it in your tree, but the default should be to build it.
On Wed, 25 Aug 2004 16:04:52 +0100, you wrote:
Was this dropped? On my laptop (a 600mhz Pentium with 128mb of ram, so not too pokey) attempting to build the winetest binary actually kills the build dead. It ends up attempting to feed ~20mb of data to gas which doesn't make it very happy. I guess I misphrased it - it's not for slower machines, it's for machines with less memory.
I have recently built wine on a P1-133 with 64MB of memory (with success). You should never be out of memory with enough swap.
Rein.
On Thu, 26 Aug 2004, Rein Klazes wrote:
On Wed, 25 Aug 2004 16:04:52 +0100, you wrote:
Was this dropped? On my laptop (a 600mhz Pentium with 128mb of ram, so not too pokey) attempting to build the winetest binary actually kills the build dead. It ends up attempting to feed ~20mb of data to gas which doesn't make it very happy. I guess I misphrased it - it's not for slower machines, it's for machines with less memory.
I have recently built wine on a P1-133 with 64MB of memory (with success). You should never be out of memory with enough swap.
In my case it is a free space on the "/" filesystem which I get running out of. Knowing the fact I like to live with a very small amount of a free space on the "/" I should complain only to myself.
On Wed, 25 Aug 2004, Alexandre Julliard wrote:
Mike Hearn m.hearn@signal.qinetiq.com writes:
There's not much reason to run the entire winetest binary on Wine itself, so why do we always build it ?
Because code that doesn't get built rots very quickly. You can disable it in your tree, but the default should be to build it.
And how exactly can I disable it? By editing wineinstall script?
And how exactly can I disable it? By editing wineinstall script?
Nah, just do what I did. There's a magic command you can put at the top of the makefile which leaves it out: look at the patch to see how to do it. Then run ./config.status and winetest will no longer be built.
-
Alexandre Julliard -
Mike Hearn -
Rein Klazes -
Saulius Krasuckas