Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Thu, 16 Dec 2004 11:21:38 -0800
From: Yitzchak Scott-Thoennes <sthoenna AT efn DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: Anyone got latex2html to work on cygwin??  Fatal (use l2hconf): l2hconf.pm
Message-ID: <20041216192138.GA2004@efn.org>
References: <20041216101048 DOT 20227 DOT qmail AT web90103 DOT mail DOT scd DOT yahoo DOT com> <Pine DOT GSO DOT 4 DOT 61 DOT 0412161228320 DOT 2298 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.61.0412161228320.2298@slinky.cs.nyu.edu>
User-Agent: Mutt/1.4.1i
Organization: bs"d
X-IsSubscribed: yes

On Thu, Dec 16, 2004 at 12:51:51PM -0500, Igor Pechtchanski wrote:
> On Thu, 16 Dec 2004, bill BW wrote:
> Nor should it.  The l2hconf.pm is not executed via the shell, but via the
> "use()" function, which ignores the shebang line altogether.  FWIW, I
> think the invalid shebang is there exactly to prevent running that file
> via the shell (unless your system has perl in the root directory).
> 
> > more information:
> >
> > $ which perl
> > /usr/bin/perl
> >
> > $ perl --version
> > This is perl, v5.8.5 built for
> > cygwin-thread-multi-64int
> >
> > Why does it say '64int' there? my machine is
> > 32 bit P4.
> 
> This means it supports 64-bit functions, that's all.

Means perl was built to use 64 bit signed and unsigned integer types.
That string is supposed to contain the most common build options that
produce binary incompatibility between one perl build and another.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/