Thread: [Module::Build] latest cygwin installation issue
Status: Beta
Brought to you by:
kwilliams
|
From: Terrence B. <met...@ur...> - 2003-10-08 15:29:18
|
This first issue is trivial, but here it is using Perl-5.8.0.
~/.cpan/build/Module-Build-0.20 $ ls
Build Changes MANIFEST Makefile README lib
Build.PL INSTALL.txt META.yml Makefile.PL _build t
~/.cpan/build/Module-Build-0.20 $ less README
~/.cpan/build/Module-Build-0.20 $ perl Makefile.PL PREFIX=$PREFIX
perl Build.PL config=prefix=/home/metaperl/install
Checking whether your kit is complete...
Looks good
Deleting Build
Removed previous script 'Build'
Creating new 'Build' script for 'Module-Build' version '0.20'
~/.cpan/build/Module-Build-0.20 $ ./Build 2> Build.err > Build.out
~/.cpan/build/Module-Build-0.20 $
--------------------------------
Build.err:
Can't open blib/libdoc/Module::Build::Platform::Unix.3pm for writing: No
such file or directory
at
/home/metaperl/.cpan/build/Module-Build-0.20/lib/Module/Build/Base.pm
line 1286
----------------------------------
Build.out:
lib/Module/Build/Platform/darwin.pm ->
blib/lib/Module/Build/Platform/darwin.pm
lib/Module/Build/Platform/MacOS.pm ->
blib/lib/Module/Build/Platform/MacOS.pm
lib/Module/Build/Compat.pm -> blib/lib/Module/Build/Compat.pm
lib/Module/Build/Platform/RiscOS.pm ->
blib/lib/Module/Build/Platform/RiscOS.pm
lib/Module/Build/Platform/VOS.pm -> blib/lib/Module/Build/Platform/VOS.pm
lib/Module/Build/Platform/Windows.pm ->
blib/lib/Module/Build/Platform/Windows.pm
lib/Module/Build/Platform/Unix.pm -> blib/lib/Module/Build/Platform/Unix.pm
lib/Module/Build/Platform/Amiga.pm ->
blib/lib/Module/Build/Platform/Amiga.pm
lib/Module/Build/Base.pm -> blib/lib/Module/Build/Base.pm
lib/Module/Build/Platform/EBCDIC.pm ->
blib/lib/Module/Build/Platform/EBCDIC.pm
lib/Module/Build/Platform/MPEiX.pm ->
blib/lib/Module/Build/Platform/MPEiX.pm
lib/Module/Build/Platform/VMS.pm -> blib/lib/Module/Build/Platform/VMS.pm
lib/Module/Build.pm -> blib/lib/Module/Build.pm
lib/Module/Build/PPMMaker.pm -> blib/lib/Module/Build/PPMMaker.pm
lib/Module/Build/Cookbook.pm -> blib/lib/Module/Build/Cookbook.pm
lib/Module/Build/Platform/Default.pm ->
blib/lib/Module/Build/Platform/Default.pm
Manifying blib/lib/Module/Build/Platform/Unix.pm ->
blib/libdoc/Module::Build::Platform::Unix.3pm
|
|
From: Ken W. <ke...@ma...> - 2003-10-10 20:50:16
|
Hi Terrence, So, this bug is that it doesn't respect PREFIX, or that it uses '::' strings in the manpage names? The latter has been fixed for the next release. The former may not be fixed anytime soon, and perhaps deserves at least a warning (possibly a die()) when encountered. -Ken On Wednesday, October 8, 2003, at 10:29 AM, Terrence Brannon wrote: > This first issue is trivial, but here it is using Perl-5.8.0. > > ~/.cpan/build/Module-Build-0.20 $ ls > Build Changes MANIFEST Makefile README lib > Build.PL INSTALL.txt META.yml Makefile.PL _build t > ~/.cpan/build/Module-Build-0.20 $ less README > ~/.cpan/build/Module-Build-0.20 $ perl Makefile.PL > PREFIX=$PREFIX > perl Build.PL config=prefix=/home/metaperl/install > Checking whether your kit is complete... > Looks good > Deleting Build > Removed previous script 'Build' > Creating new 'Build' script for 'Module-Build' version '0.20' > ~/.cpan/build/Module-Build-0.20 $ ./Build 2> Build.err > > Build.out > ~/.cpan/build/Module-Build-0.20 $ > > -------------------------------- > > Build.err: > > Can't open blib/libdoc/Module::Build::Platform::Unix.3pm for writing: > No such file or directory > at > /home/metaperl/.cpan/build/Module-Build-0.20/lib/Module/Build/Base.pm > line 1286 > > ---------------------------------- > > Build.out: > > lib/Module/Build/Platform/darwin.pm -> > blib/lib/Module/Build/Platform/darwin.pm > lib/Module/Build/Platform/MacOS.pm -> > blib/lib/Module/Build/Platform/MacOS.pm > lib/Module/Build/Compat.pm -> blib/lib/Module/Build/Compat.pm > lib/Module/Build/Platform/RiscOS.pm -> > blib/lib/Module/Build/Platform/RiscOS.pm > lib/Module/Build/Platform/VOS.pm -> > blib/lib/Module/Build/Platform/VOS.pm > lib/Module/Build/Platform/Windows.pm -> > blib/lib/Module/Build/Platform/Windows.pm > lib/Module/Build/Platform/Unix.pm -> > blib/lib/Module/Build/Platform/Unix.pm > lib/Module/Build/Platform/Amiga.pm -> > blib/lib/Module/Build/Platform/Amiga.pm > lib/Module/Build/Base.pm -> blib/lib/Module/Build/Base.pm > lib/Module/Build/Platform/EBCDIC.pm -> > blib/lib/Module/Build/Platform/EBCDIC.pm > lib/Module/Build/Platform/MPEiX.pm -> > blib/lib/Module/Build/Platform/MPEiX.pm > lib/Module/Build/Platform/VMS.pm -> > blib/lib/Module/Build/Platform/VMS.pm > lib/Module/Build.pm -> blib/lib/Module/Build.pm > lib/Module/Build/PPMMaker.pm -> blib/lib/Module/Build/PPMMaker.pm > lib/Module/Build/Cookbook.pm -> blib/lib/Module/Build/Cookbook.pm > lib/Module/Build/Platform/Default.pm -> > blib/lib/Module/Build/Platform/Default.pm > Manifying blib/lib/Module/Build/Platform/Unix.pm -> > blib/libdoc/Module::Build::Platform::Unix.3pm > > > > > > |
|
From: Terrence B. <met...@ur...> - 2003-10-11 03:14:40
|
Ken Williams wrote: > Hi Terrence, > > So, this bug is that it doesn't respect PREFIX, or that it uses '::' > strings in the manpage names? The latter has been fixed for the next > release. The former may not be fixed anytime soon, and perhaps > deserves at least a warning (possibly a die()) when encountered. > just the latter Ken... > -Ken > > On Wednesday, October 8, 2003, at 10:29 AM, Terrence Brannon wrote: > >> This first issue is trivial, but here it is using Perl-5.8.0. >> >> ~/.cpan/build/Module-Build-0.20 $ ls >> Build Changes MANIFEST Makefile README lib >> Build.PL INSTALL.txt META.yml Makefile.PL _build t >> ~/.cpan/build/Module-Build-0.20 $ less README >> ~/.cpan/build/Module-Build-0.20 $ perl Makefile.PL PREFIX=$PREFIX >> perl Build.PL config=prefix=/home/metaperl/install >> Checking whether your kit is complete... >> Looks good >> Deleting Build >> Removed previous script 'Build' >> Creating new 'Build' script for 'Module-Build' version '0.20' >> ~/.cpan/build/Module-Build-0.20 $ ./Build 2> Build.err > >> Build.out >> ~/.cpan/build/Module-Build-0.20 $ >> >> -------------------------------- >> >> Build.err: >> >> Can't open blib/libdoc/Module::Build::Platform::Unix.3pm for writing: >> No such file or directory >> at >> /home/metaperl/.cpan/build/Module-Build-0.20/lib/Module/Build/Base.pm >> line 1286 >> >> ---------------------------------- >> >> Build.out: >> >> lib/Module/Build/Platform/darwin.pm -> >> blib/lib/Module/Build/Platform/darwin.pm >> lib/Module/Build/Platform/MacOS.pm -> >> blib/lib/Module/Build/Platform/MacOS.pm >> lib/Module/Build/Compat.pm -> blib/lib/Module/Build/Compat.pm >> lib/Module/Build/Platform/RiscOS.pm -> >> blib/lib/Module/Build/Platform/RiscOS.pm >> lib/Module/Build/Platform/VOS.pm -> >> blib/lib/Module/Build/Platform/VOS.pm >> lib/Module/Build/Platform/Windows.pm -> >> blib/lib/Module/Build/Platform/Windows.pm >> lib/Module/Build/Platform/Unix.pm -> >> blib/lib/Module/Build/Platform/Unix.pm >> lib/Module/Build/Platform/Amiga.pm -> >> blib/lib/Module/Build/Platform/Amiga.pm >> lib/Module/Build/Base.pm -> blib/lib/Module/Build/Base.pm >> lib/Module/Build/Platform/EBCDIC.pm -> >> blib/lib/Module/Build/Platform/EBCDIC.pm >> lib/Module/Build/Platform/MPEiX.pm -> >> blib/lib/Module/Build/Platform/MPEiX.pm >> lib/Module/Build/Platform/VMS.pm -> >> blib/lib/Module/Build/Platform/VMS.pm >> lib/Module/Build.pm -> blib/lib/Module/Build.pm >> lib/Module/Build/PPMMaker.pm -> blib/lib/Module/Build/PPMMaker.pm >> lib/Module/Build/Cookbook.pm -> blib/lib/Module/Build/Cookbook.pm >> lib/Module/Build/Platform/Default.pm -> >> blib/lib/Module/Build/Platform/Default.pm >> Manifying blib/lib/Module/Build/Platform/Unix.pm -> >> blib/libdoc/Module::Build::Platform::Unix.3pm >> >> >> >> >> >> > |
|
From: Ken W. <ke...@ma...> - 2003-10-11 15:26:14
|
On Friday, October 10, 2003, at 10:14 PM, Terrence Brannon wrote: > Ken Williams wrote: > >> Hi Terrence, >> >> So, this bug is that it doesn't respect PREFIX, or that it uses '::' >> strings in the manpage names? The latter has been fixed for the next >> release. The former may not be fixed anytime soon, and perhaps >> deserves at least a warning (possibly a die()) when encountered. >> > just the latter Ken... Great, thanks. -Ken |