Rob@desktop2 ~
$ which perl
/usr/bin/perl

Rob@desktop2 ~
$ which gcc
/usr/bin/gcc

Rob@desktop2 ~
$ which make
/usr/bin/make

Rob@desktop2 ~
$ perl -e 'print $^X'
/usr/bin/perl.exe

Rob@desktop2 ~
$ perl -V:make
make='make';

Rob@desktop2 ~
$ perl -V:cc
cc='gcc';

Rob@desktop2 ~
$ perl -v

This is perl, v5.8.8 built for cygwin-thread-multi-64int
(with 8 registered patches, see perl -V for more detail)

Copyright 1987-2006, Larry Wall

Perl may be copied only under the terms of either the Artistic License
+ or the
GNU General Public License, which may be found in the Perl 5 source ki
+t.

Complete documentation for Perl, including FAQ lists, should be found 
+on
this system using "man perl" or "perldoc perl".  If you have access to
+ the
Internet, point your browser at http://www.perl.org/, the Perl Home Pa
+ge.
[download]

I tried these, and I got exactly the same answers.

I use windows. So when I started working with perl, I downloaded Activeperl for windows; however later decided to switch to cygwin and run cygwin version of perl from cygwin. Now that I want to add PDL to perl on cygwin, I am getting all these problem.

I don't know why cygwin is trying to use Dev-cpp make. I tried to removing Dev-cpp and Activeperl from windows path, but still giving me the same problem. Any suugestions?

Thank you for your help

I tried to removing Dev-cpp and Activeperl from windows path

As long as their listing in $PATH occurs after /usr/bin, their presence should not matter - assuming that /usr/bin contains a 'make.exe', a 'ggc.exe', and a 'perl.exe' etc. (I wonder if it's the cpan shell that's doing something to stuff things up. I'm assuming that we're in the cpan shell that belongs to usr/bin/perl, not ActivePerl.)

So, it gets to the point where we need to see the 'perl Makefile.PL' and 'make' output.

'cd' to some location (say ~/modules) and manually extract the PDL source (tar zxvf /location_of/PDL-2.4.6.tar.gz)

Then run perl Makefile.PL >p.txt 2>&1 followed by make >m.txt 2>&1. Then send us a copy'n'paste of p.txt. It may be that m.txt is too large to post to perlmonks (depending upon when the error occurs). If it's not too big to post to perlmonks, then send us a copy'n'paste of it, too. Otherwise it would probably be best to move this over to the PDL list where you can send copies of 'p.txt' and 'm.txt' as attachments.

Cheers,
Rob