At 11.34 7/30/97, Terje Bless wrote: >At 09:56 -0500 30-07-97, Chris Nandor wrote: >>On my big UltraSPARC Solaris box at work, the syadmin wanted >>all GNU-type stuff in /opt/gnu ... so I installed perl there, but made it >>respond to "#!/usr/bin/perl" on the shebang line (which is where perl is on >>our other machines) during configuration. > >The shebang line isn't interpreted by perl. It's there to allow a different >interpreter for the script then the current shell > >Nothing you do to the perl binary will let it catch the shebang line before >the shell. If "/usr/bin/perl" doesn't exist your shell will cry foul before >"/opt/gnu/perl" ever sees it. > >What you *can* do at "sh ./configure" time is to specify a different name >for the binary so you can call it "baz" and still use embedded commandline >switches on the shebang line. Which is no different from what I said. I just didn't explain it fully. I am fully aware that what happened at configure time was that a symbolic link was created at /usr/bin/perl -> /opt/gnu/biun/perl. But the effect is that all the perl stuff (except the copy of the executable) is in /opt/gnu but you can put /usr/bin/perl on the shebang line. And the whole point is that it doesn't matter at all where perl is. You can call it by whatever you want from your scripts (so long as it points to a symbolic link or perl itself), and you can install it where you want. -- Chris Nandor pudge@pobox.com http://pudge.net/ %PGPKey=('B76E72AD',[1024,'0824 090B CE73 CA10 1FF7 7F13 8180 B6B6']) ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch