Re: [Module::Build] Does ./Build work on Windows?

[<and...@fr...>]

>>>>> On Mon, 30 Jan 2006 16:54:08 -0600, Ken Williams <ke...@ma...> said:

  > On Jan 30, 2006, at 3:10 PM, Andreas J. Koenig wrote:

 >>>>>>> On Mon, 30 Jan 2006 14:05:45 -0600, Ken Williams
 >>>>>>> <ke...@ma...> said:
 >> 
 >>> I haven't been pulling my weight in testing the CPAN.pm releases (I
 >>> have no great Windows box to test it on, but I could at least do Unix
 >>> testing).  Should it be generally sufficient to run the regression
 >>> tests, or would someone need to install it and play with it for a
 >>> while too?
 >> 
 >> The latter, please. My regression tests are just an alibi.

  > I just pulled down 1.83_59 and installed it, and I recommend the
  > following patch:

  > ===========================================
  > --- Makefile.PL~	Wed Jan 25 06:05:22 2006
  > +++ Makefile.PL	Mon Jan 30 16:49:59 2006
  > @@ -134,12 +134,6 @@

  >  package MY;

  > -sub macro {
  > -    q{
  > -LC_ALL=en_GB.utf8
  > -}
  > -}
  > -
  >  sub postamble {
  >    q{
  >  setversion:
  > ===========================================

  > The en_GB.utf8 locale isn't recognized on my platform (Mac OS X
  > 10.3.9) so I get a million warnings about it during the build & tests.

This is completely incomprehensible to me. The LC_ALL macro is only
used during 'make chlog' which you certainly have not called.

'make', 'make test', and 'make install' should not be influenced by
this macro. Is it so on OS X that macros are magically transposed into
environment variables?

What if you rename the macro like in this pseudo patch?

-LC_ALL=en_GB.utf8
+LC_ALL_XXX=en_GB.utf8



-- 
andreas