> "Michael" == Michael Jinks <[EMAIL PROTECTED]> writes:
Michael> Here's the layout: On the cd is a shell script called
Michael> install. It tries to figure out which kind of system it's
Michael> running on, and then calls another program based on its
Michael> guess. The systems it
Andrew Burton wrote:
> I'm confused.
>
> My previous comments were based almost entirely on your post in the
> mailing list that the error was on line 1 of a perl script.
I think I used that term improperly. Maybe I should have said "perl
executable"?
> That's
> almost always #!/bin/perl or s
I missed the whole point in that last post. The install _script_ is
actually fine; it's the app that gets called from the script (I'm pretty
sure) which is causing the failure. I've looked at the app and it's a
binary, so if I'm going to make it work I'll have to bend my system to it,
not the ot
Andrew Burton wrote:
> I take it you've edited the install script?
No
> Did you do it with a
> native UNIX editor? I suspect not.
:)
If I were in the habit of using non-Unix stuff, I wouldn't need to shoehorn
Notes onto my Linux box. . .
vi is the Way. . .
But there's no telling what idi
My current low-priority project is getting Lotus Notes for Unix to
install on my RedHat box. The Notes installer invokes a perl script
based on the architecture where it thinks it's running; I've gotten as
far as fooling it into thinking that my machine is a Sun running on an
x86, but the perl ap
