Robert Wyatt wrote:
> Peter O'Gorman wrote:
>> On 07/22/2010 04:08 AM, Daniel E. Macks wrote:
>>
>>> 2. Figure out a shell env var or other way to make sure that the
>>> spawned interp is run with the correct arch. At various times in
>>> various contexts, we use ARCHFLAGS="" (I think that only
Peter O'Gorman wrote:
On 07/22/2010 04:08 AM, Daniel E. Macks wrote:
2. Figure out a shell env var or other way to make sure that the
spawned interp is run with the correct arch. At various times in
various contexts, we use ARCHFLAGS="" (I think that only affects the
compiling of C-code modu
On 07/22/2010 04:08 AM, Daniel E. Macks wrote:
>
> 2. Figure out a shell env var or other way to make sure that the
> spawned interp is run with the correct arch. At various times in
> various contexts, we use ARCHFLAGS="" (I think that only affects the
> compiling of C-code modules?). That is alwa
So it's "well-known" to those that know that selftest suites ('make
test') of the -pm5100 variant of many perlmodule packages fails on OS
X 10.6 when fink is configured for 32-bit (arch i386). If you didn't
know, now you do. I spent a few hours hacking the internals of
ExtUtils::MakeMaker and Test:
