IIRC, install Inline::Cpp should answer some questions before installation, that might lead to this problem?
On Tue, Aug 14, 2012 at 6:51 AM, David Oswald <[email protected]> wrote: > I just got a strange bug report on Inline::CPP, and don't see what the > issue is. This is against the current version, v0.39. > > Here's the report: > > ---------------------------- > > I tried to install Inline::Cpp into Strawberry perl running under > Windows XP (32 bit) but the build.log records FAIL: > > cpanm (App::cpanminus) 1.5013 on perl 5.014002 built for > MSWin32-x86-multi-thread > Work directory is /.cpanm/work/1344884468.1676 > You have make C:\Dwimperl\c\bin\dmake.exe > You have LWP 6.03 > Falling back to Archive::Tar 1.80 > Searching Inline::CPP on cpanmetadb ... > --> Working on Inline::CPP > Fetching http://www.cpan.org/authors/id/D/DA/DAVIDO/Inline-CPP-0.39.tar.gz > -> OK > Unpacking Inline-CPP-0.39.tar.gz > Entering . > META.yml not found or unparsable. Fetching META.yml from search.cpan.org > Configuring Inline-CPP-0.39 > -> N/A > -> FAIL The distribution doesn't have a proper Makefile.PL/Build.PL > See \.cpanm\build.log for details. > > Any ideas on what I can do to install it ?? > > ------------------------------- > > To investigate, I attempted "cpanm Inline::CPP --reinstall", and got > the following different message: > > $ cpanm Inline::CPP --reinstall > --> Working on Inline::CPP > Fetching http://www.cpan.org/authors/id/D/DA/DAVIDO/Inline-CPP-0.39.tar.gz > ... OK > ! Bad archive: Inline-CPP-0.39.tar.gz > ! Failed to unpack Inline-CPP-0.39.tar.gz: no directory > ! Failed to fetch distribution Inline-CPP-0.39 > > > Yet if I download the tarball myself (the link above works fine, for > example), and unpack it with 'tar -zxf Inline-CPP-0.39-tar.gz', it > unpacks fine into ./Inline-CPP-0.39, and from there I'm able to > perform the mantra without any problems. > > Also, if I remove the module from my system and then install it via > the 'cpan' tool (instead of cpan minus), it works: > > cpan Inline::CPP > > ...works fine. > > Any thoughts? Can anyone confirm the behavior? > > > -- > > David Oswald > [email protected] >
