RE: [Module::Build] Problem building XS modules on AIX

[James.FitzGibbon <Jam...@ta...>]

It works to build Pod::Coverage 0.12 on AIX, but the M::B XS test itself
fails.  It only fails two of ten tests, and those are related to
cleanup:

t/xs............ok 8/10Can't remove directory blib/arch/auto/XSTest: Do
not specify an existing file. at
/home_dir/jfitzgi/work/Module-Build-0.21/blib/lib/Module/Build/Base.pm
line 1792
Can't remove directory blib/arch/auto: Do not specify an existing file.
at
/home_dir/jfitzgi/work/Module-Build-0.21/blib/lib/Module/Build/Base.pm
line 1792
Can't remove directory blib/arch: Do not specify an existing file. at
/home_dir/jfitzgi/work/Module-Build-0.21/blib/lib/Module/Build/Base.pm
line 1792
Can't remove directory blib: Do not specify an existing file. at
/home_dir/jfitzgi/work/Module-Build-0.21/blib/lib/Module/Build/Base.pm
line 1792
# Test 9 got: 'Couldn't remove 'blib': Do not specify an existing file.
' (t/xs.t at line 72)
#   Expected: ''
# Failed test 10 in t/xs.t at line 75
t/xs............FAILED tests 9-10
        Failed 2/10 tests, 80.00% okay
Failed Test Stat Wstat Total Fail  Failed  List of Failed
------------------------------------------------------------------------
-------
t/xs.t                    10    2  20.00%  9-10
1 test skipped.
Failed 1/10 test scripts, 90.00% okay. 2/157 subtests failed, 98.73%
okay.

The test code is:

eval {$m->dispatch('realclean')};
ok $@, '';

# Make sure blib/ is gone after 'realclean'
ok not -e 'blib';

So, this may not be the fault of the patch but instead bad assumptions
on
the part of the test.  On the other hand, this same test passed with the
second revision of the patch (the current one being #3 I believe).

It may also be related to me running the test on an NFS mounted homedir.
I tried it on a local disk and it passed.  So, I'm willing to write off
the
failures to the assumptions of the test suite and say it's a good
candidate for
then next release unless someone has an OS/2 or VMS box to pound on it
with.

Thanks to everyone who helped.

-----Original Message-----
From: Randy W. Sims [mailto:Ra...@Th...]=20
Sent: Tuesday, November 18, 2003 8:09 PM
To: mod...@li...
Cc: James.FitzGibbon; Michael G Schwern
Subject: Re: [Module::Build] Problem building XS modules on AIX


On 11/18/2003 10:36 AM, James.FitzGibbon wrote:
> I've updated Randy's patch to find the .exp files in the right place=20
> on AIX, but I don't have the necessary Windows environment to see if=20
> I've broken things there.

I've updated James' update of my patch ;) There were some Windows=20
problems. I think ExtUtils::Mksymlists is buggy on Windows; it dies if=20
you don't pass in something for some of the arguments even if its an=20
empty array or hash ref. I also changed it so that it generates the=20
def/exp file in the source directory and put the correct names into=20
add_to_cleanup().

James, can you please run this through the test suite one more time?

Michael, VMS wasn't calling Mksymlists before though it looks like it=20
should have. Looking at EU::Mksymlists lines 53-58, I changed M::B to=20
now invoke Mksymlists if grep $^O, qw(aix MacOS MSWin32 os2 VMS). Is=20
this correct?

> Perhaps what is needed is to update EU::Mksymlists to both export the=20
> platform-specific extensions as constants and return the canonical=20
> path to the written file back to it's
> caller so that link_c() in M::B can act more intelligently.
>=20
> Thanks.

Seems like a harmless but beneficial change, since the name of the file=20
can vary depending on $^O, and there aught to be some way to find out=20
what it is without read the source.

Randy.