On 28 May 2014 22:22, Nigel Horne <n...@bandsman.co.uk> wrote:
> That doesn't address the main point: I have not customized anything.
Sometimes Cygwin just gets rusty though.
> Have you tried to reproduce the problem?
No, but I tried installing on my Cygwin here:
-----------------------------------------
Cygwin environment on Windows
[ben@grapefruit] {22:06 35} ~ 501 $ cpanm Encode::Detective
!
! Can't write to /usr/lib/perl5/site_perl/5.14 and /usr/local/bin:
Installing modules to /cygdrive/c/Users/ben/perl5
! To turn off this warning, you have to do one of the following:
! - run me as a root or with --sudo option (to install to
/usr/lib/perl5/site_perl/5.14 and /usr/local/bin)
! - Configure local::lib your existing local::lib in this shell to
set PERL_MM_OPT etc.
! - Install local::lib by running the following commands
!
! cpanm --local-lib=~/perl5 local::lib && eval $(perl -I
~/perl5/lib/perl5/ -Mlocal::lib)
!
--> Working on Encode::Detective
Fetching http://www.cpan.org/authors/id/B/BK/BKB/Encode-Detective-0.06.tar.gz
... OK
Configuring Encode-Detective-0.06 ... OK
Building and testing Encode-Detective-0.06 ...OK
Successfully installed Encode-Detective-0.06
1 distribution installed
[ben@grapefruit] {22:08 28} ~ 502 $ locate crypt.h
[ben@grapefruit] {22:09 05} ~ 503 $ more /usr/include/crypt.h
/* encrypt.h - API to 56 bit DES encryption via calls
encrypt(3), setkey(3) and crypt(3)
Copyright (C) 1991 Jochen Obalek
----------------------------------------------------
As seen above, it looks OK but this is not the same as your setup so I
cannot say I have fully tried to reproduce the problem. The text at
the top "Cygwin environment on Windows" is printed by my .bashrc.
I know that Cygwin is prone to developing problems if it's not updated
regularly by re-running "setup.exe". I think I last ran it a week or
two ago.
> That would help a lot to find out
> a fix.
I'm very happy to find a fix. The only thing I can think of is that
the Cygwin is getting rusty and needs to have setup.exe run again.
Because the error doesn't seem to have much to do with my module, I
decided to raise the issue with you. However it may actually be my
module which is at fault, for example ppport.h may be a wrong version
or something.
