Hi,
Isn't the problem that on windows using :
POD2MAN=$(SH) pod2man
will try and use perl from Cygwin in a bash shell, in which case you must have perl installed in your cygwin environment.
and using
POD2MAN=pod2man
requires you to have "windows" perl installed and perl in your path.
This became a requirement when allways building the documents was added to the make process.
Best regards
Anders
-----Original Message-----
From: ethereal-dev-bounces@xxxxxxxxxxxx
[mailto:ethereal-dev-bounces@xxxxxxxxxxxx]On Behalf Of Ulf Lamping
Sent: den 22 januari 2004 22:01
To: Guy Harris
Cc: Ethereal; Yaniv Kaul
Subject: Re: [Ethereal-dev] patch to packet-http.c (0.9.16) - support
for ShoutCast's 'ICY' reply
Guy Harris wrote:
>
> On Jan 21, 2004, at 1:26 AM, Yaniv Kaul wrote:
>
>> In the lastest snapshot (20Jan04), there is a problem in config.nmake:
>>
>> POD2MAN=$(SH) pod2man
>> POD2HTML=$(SH) pod2html
>>
>> should be:
>>
>> POD2MAN=pod2man
>> POD2HTML=pod2html
>
>
> That dates back to
>
> revision 1.69
> date: 2003/12/22 21:34:13; author: ulfl; state: Exp; lines: +3 -3
> calling pod2man and pod2html indirectly through the bash
>
> I think that change was made because in some environments
>
> POD2MAN=pod2man
> POD2HTML=pod2html
>
> *didn't* work. (Windows doesn't, as far as I know, know about "#!".)
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
Hi Yaniv!
Yes, the changes were made, as on the usual win32 platforms, a perl
interpreter is *not* in the PATH.
So a call to pod2man will fail, as the cmd.exe (or whatever command.exe)
will not try to resolve the !/bin/perl statement at the top of the file.
Could you describe the problem you have?
Regards, ULFL
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev