On 19 October 2010 19:20, Jan Dubois <[email protected]> wrote: > On Tue, 19 Oct 2010, Jan Dubois wrote: >> > M M -Duselargefiles -Dusemymalloc >> >> I don't understand this configuration. At least the win32/Makefile >> does not allow you to define PERL_MALLOC unless you disable USE_IMP_SYS. >> So how is this configuration different from the one below: >> >> > M M -Duselargefiles -Duseithreads -Uuseimpsys -Dusemymalloc > > Ok, so I guess it is the -Duseithreads that makes it different. :) > > I still wonder why the first configuration doesn't show a -Uuseimpsys. > The -Dusemymalloc should get ignored without it, and then the > configuration shouldn't fail at all. Or maybe this is just incorrect > reporting by the smoke harness? Or am I missing another obvious thing, > like the -Duseithreads above? >
I think the smoke harness does the build with all the Makefile options switched off by default (rather than using the defaults in the Makefile itself), and you have to explicitly switch on anything that you want. So the first configuration above doesn't need to switch off USE_IMP_SYS because it is off by default in smoke builds anyway. Switching on USE_ITHREADS with -Duseithreads also switches on USE_MULTI and USE_IMP_SYS, so if you want USE_ITHREADS and PERL_MALLOC then you have to switch off USE_IMP_SYS with -Uuseimpsys. At least, that's my recollection of it...
