Getopt::Long install problems

I've successfully installed numerous Perl modules from CPAN.  (I almost
get the feeling that I know what I am doing.)  But I downloaded the
latest release of Getopt::Long and ran 'perl Makefile.PL' which created
the Makefile, but complained that pod2man was not in the PATH (but, "Oh,
yes it is!").  Nonetheless, I ran 'make' and it gave me this message:

make:87: *** missing separator.  Stop.

So I checked out line 87 and found this line:

installman1

which I appended ='' so it looked like this:

installman1=''

This satisfied that error and then made the same complaint about line
97.  Fixed that the same way and several new errors came up complaining
about unexpected EOF while looking for matching quote...  I noticed that
there were numberous unclosed or unopened single quotes througout the
Makefile.  Obviously, something got way out of whack and I never could
fix the Makefile to the point where it ran.  What did I do wrong, or
what is wrong with Getopt::Long?  Does the fact that the supposedly
zipped tar file ends in a tar.tar extention instead of a tar.gz
extention have anything to do with my problem?  Or is this just sloppy
work on the part of the maintainer?  Anybody able to help me??

Mark

Mark J Fenbers wrote...
> Does the fact that the supposedly
>zipped tar file ends in a tar.tar extention instead of a tar.gz
>extention have anything to do with my problem?

Looks like it's *your* problem.
Before you download, the source link property should say
Getopt-Long-2.34.tar.gz. So, if your download has the name tar.tar
instead of tar.gz, your browser is not set up properly.

If your browser download it in ASCII mode, your tar ball would be
screwed up. Try download it again using wget.

wget http://www.cpan.org/modules/by-modu...ong-2.34.tar.gz

Ten uppack it using gnu tar.

tar -xzf Getopt-Long-2.34.tar.gz

Good luck.

> Looks like it's *your* problem.
> Before you download, the source link property should say
> Getopt-Long-2.34.tar.gz. So, if your download has the name tar.tar
> instead of tar.gz, your browser is not set up properly.
>
> If your browser download it in ASCII mode, your tar ball would be
> screwed up. Try download it again using wget.
>
> wget http://www.cpan.org/modules/by-modu...ong-2.34.tar.gz

I've downloaded tar.gz files many times before.  This is the first time I've
run into this.  Unfortunately, my Linux box is locked tight behind a firewal
l
and it has no direct Internet access, so I have to use a PC to get the file
and place it on a network drive, then tunnel in from the Linux box to fetch
it.  Therefore, I cannot use wget.  I tried getting the file with the latest
versions of both IE and Netscape and my results are the same, except using
Netscape I get a file extention of tar.gz instead of tar.tar...

What would cause my browser to download it in ASCII mode?

Any other ideas of what to do next?

> Looks like it's *your* problem.
> Before you download, the source link property should say
> Getopt-Long-2.34.tar.gz. So, if your download has the name tar.tar
> instead of tar.gz, your browser is not set up properly.
>
> If your browser download it in ASCII mode, your tar ball would be
> screwed up. Try download it again using wget.
>
> wget http://www.cpan.org/modules/by-modu...ong-2.34.tar.gz

I've downloaded tar.gz files many times before.  This is the first time I've
run into this.  Unfortunately, my Linux box is locked tight behind a firewal
l
and it has no direct Internet access, so I have to use a PC to get the file
and place it on a network drive, then tunnel in from the Linux box to fetch
it.  Therefore, I cannot use wget.  I tried getting the file with the latest
versions of both IE and Netscape and my results are the same, except using
Netscape I get a file extention of tar.gz instead of tar.tar...

What would cause my browser to download it in ASCII mode?

Well, I downloaded it using the FTP protocol, too.  But the 'make' command
still gave me the same results.  I does appear that the problem is in fact
with the gzipped tar file.  But I  would LOVE to be proven otherwise, as I
really need to get this done tonight...

Any other ideas of what to do next?

Mark

> Looks like it's *your* problem.
> Before you download, the source link property should say
> Getopt-Long-2.34.tar.gz. So, if your download has the name tar.tar
> instead of tar.gz, your browser is not set up properly.
>
> If your browser download it in ASCII mode, your tar ball would be
> screwed up. Try download it again using wget.
>
> wget http://www.cpan.org/modules/by-modu...ong-2.34.tar.gz

I've downloaded tar.gz files many times before.  This is the first time I've
run into this.  Unfortunately, my Linux box is locked tight behind a firewal
l
and it has no direct Internet access, so I have to use a PC to get the file
and place it on a network drive, then tunnel in from the Linux box to fetch
it.  Therefore, I cannot use wget.  I tried getting the file with the latest
versions of both IE and Netscape and my results are the same, except using
Netscape I get a file extention of tar.gz instead of tar.tar...

What would cause my browser to download it in ASCII mode?

Well, I downloaded it using the FTP protocol, too.  But the 'make' command
still gave me the same results.  I does appear that the problem is in fact
with the gzipped tar file.  But I  would LOVE to be proven otherwise, as I
really need to get this done tonight...

Any other ideas of what to do next?

Mark

> Looks like it's *your* problem.
> Before you download, the source link property should say
> Getopt-Long-2.34.tar.gz. So, if your download has the name tar.tar
> instead of tar.gz, your browser is not set up properly.
>
> If your browser download it in ASCII mode, your tar ball would be
> screwed up. Try download it again using wget.
>
> wget http://www.cpan.org/modules/by-modu...ong-2.34.tar.gz

I've downloaded tar.gz files many times before.  This is the first time I've
run into this.  Unfortunately, my Linux box is locked tight behind a firewal
l
and it has no direct Internet access, so I have to use a PC to get the file
and place it on a network drive, then tunnel in from the Linux box to fetch
it.  Therefore, I cannot use wget.  I tried getting the file with the latest
versions of both IE and Netscape and my results are the same, except using
Netscape I get a file extention of tar.gz instead of tar.tar...

What would cause my browser to download it in ASCII mode?

Well, I downloaded it using the FTP protocol, too.  But the 'make' command
still gave me the same results.  I does appear that the problem is in fact
with the gzipped tar file.  But I  would LOVE to be proven otherwise, as I
really need to get this done tonight...

Any other ideas of what to do next?

Mark

> Looks like it's *your* problem.
> Before you download, the source link property should say
> Getopt-Long-2.34.tar.gz. So, if your download has the name tar.tar
> instead of tar.gz, your browser is not set up properly.
>
> If your browser download it in ASCII mode, your tar ball would be
> screwed up. Try download it again using wget.
>
> wget http://www.cpan.org/modules/by-modu...ong-2.34.tar.gz

I've downloaded tar.gz files many times before.  This is the first time I've
run into this.  Unfortunately, my Linux box is locked tight behind a firewal
l
and it has no direct Internet access, so I have to use a PC to get the file
and place it on a network drive, then tunnel in from the Linux box to fetch
it.  Therefore, I cannot use wget.  I tried getting the file with the latest
versions of both IE and Netscape and my results are the same, except using
Netscape I get a file extention of tar.gz instead of tar.tar...

What would cause my browser to download it in ASCII mode?

Well, I downloaded it using the FTP protocol, too.  But the 'make' command
still gave me the same results.  I does appear that the problem is in fact
with the gzipped tar file.  But I  would LOVE to be proven otherwise, as I
really need to get this done tonight...

Any other ideas of what to do next?

Mark

Mark J Fenbers wrote:

> I've successfully installed numerous Perl modules from CPAN.  (I almost
> get the feeling that I know what I am doing.)  But I downloaded the
> latest release of Getopt::Long and ran 'perl Makefile.PL' which created
> the Makefile, but complained that pod2man was not in the PATH (but, "Oh,
> yes it is!").  Nonetheless, I ran 'make' and it gave me this message:
>
> make:87: *** missing separator.  Stop.
>
> So I checked out line 87 and found this line:
>
> installman1

Shouldn't this be "INSTALLMAN1DIR"?  I think your MakeMaker isn't
producing the Makefile correctly.  What version of Perl and
ExtUtils::MakeMaker are you using?

Run these commands:
perl --version
perl -MExtUtils::MakeMaker -e 'print "$ExtUtils::MakeMaker::VERSION\n";'

I don't think it's an issue of your tar file getting corrupted.  If it
had, most likely you wouldn't be able to extract the files at all.

I'm using Perl 5.8.4, ExtUtils::MakeMaker 6.17, gmake 3.80 on FreeBSD
4.9.  I tried downloading and building Getopt::Long, using the cpan
shell, and it worked fine.

Regards,
Bill K.

Perl 5.8.0
MakeMaker 6.03
make Gnu 3.79.1
RedHat 9

Mark

Bill Karwin wrote:

> Mark J Fenbers wrote:
> 
>
> Shouldn't this be "INSTALLMAN1DIR"?  I think your MakeMaker isn't
> producing the Makefile correctly.  What version of Perl and
> ExtUtils::MakeMaker are you using?
>
> Run these commands:
>    perl --version
>    perl -MExtUtils::MakeMaker -e 'print "$ExtUtils::MakeMaker::VERSION\n";
'
>
> I don't think it's an issue of your tar file getting corrupted.  If it
> had, most likely you wouldn't be able to extract the files at all.
>
> I'm using Perl 5.8.4, ExtUtils::MakeMaker 6.17, gmake 3.80 on FreeBSD
> 4.9.  I tried downloading and building Getopt::Long, using the cpan
> shell, and it worked fine.
>
> Regards,
> Bill K.

Mark J Fenbers <Mark.Fenbers@noaa.gov> wrote in
news:4161E0C7.55C3F5B0@noaa.gov:

Mark:

I am going to suggest that you read the posting guidelines for this group
before proceeding any further.

Avoid top-posting.

> Attachment decoded: untitled-2.txt

Avoid attachments.

And the main reason I am even bothering to write this, do not post multiple
copies of the same message. Given the fact that you posted the exact same
message at 6:49, 6:55, 6:58, 7:00, 7:03, 7:08, and 7:11 EST I am inclined
not to think it was by accident.

Sinan.