Here is something.  Maybe not very much.  The only reason I offer this is
that the verbiage ""No such file or directory at -e line" happened to me
once in PAR context.  I posted the problem at

http://www.mail-archive.com/[EMAIL PROTECTED]/msg01315.html

and got a number of replies on it.   A lot of it was over my head (I don't
know C) but maybe you can understand it.

On the other hand, there are a number of google matches for "No such file or
directory at -e line" that clearly have nothing at all to do with PAR.

Nothing ventured, nothing gained.  Hope you can gain from this.



----- Original Message ----- 
From: "Bob McGowan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 29, 2004 4:17 PM
Subject: Cross platform(?) problem


> Hi,
>
> I've only just begun using PAR and this may turn out to be some sort of
user
> error.  But I could not find any reference to the type of problem I'm
seeing in
> any postings for the last year and half (or so).
>
> The basic problem is that a set of scripts, which use DBI and DBD::Oracle,
work
> on two Red Hat systems but fail on a third with the error:
>
> No such file or directory at -e line 671
>
> Following are the gory details:
>
> I created the PAR file, a standalone executable, on my development
machine,
> which runs RedHat 7.3, as a 'multi-script' archive.  On the machine on
which I
> created it, it works fine.  The machine has all the environment variables
and
> library paths to support Oracle OCI and the DBD::Oracle set.  However, the
> Oracle home only contains the minimum set of files required to support the
> application.
>
> I copied the archive to a Red Hat Enterprise WS, 3.0, system and created
hard
> links for the various script names.  The environment matches that of the
above
> system, since I simply copied my login rc files from one to the other.
The
> Oracle setup is different, in that Oracle home points to the same place as
it
> does above but the library config (ld.so.conf) points to the full Oracle
install
> location.  The PAR file works as expected here as well.
>
> The third system, Red Hat 7.3, is installed under VMware as a guest OS,
running
> with/on the Enterprise WS system.  This system does not have any of the
login rc
> scripts (it's pretty much pristine, as installed).  This is the machine
that
> generates the error.  I have tried every combination I can think of for
> variables, libraries (minimal and full).  All to no avail.
>
> Thanks for your help.
>
> Bob McGowan
>

Reply via email to