On 1/18/13 2:58 PM, Ralph Lange wrote:
> Hi Murali,
>
> one way to get around this (this is what the EPICS build system does)
> would be not to use the hashbang by explicitly calling perl with the
> script as argument:
> perl ./bin/linux-x86_64-debug/capr.pl
>
> Admittedly, this avoids the issue and does not fix it.
>
> A more elegant portable solution is replacing the hashbang with
>
> eval 'exec perl -S $0 ${1+"$@"}' # -*- Mode: perl -*-
> if 0;
>
> That will find perl in the PATH.
?? I would say the correct thing to do would be for the hashbang in
capr.pl (and all others) to be set correctly based on the PERL variable
from the EPICS build system at build time.
Lewis
- References:
- Alter Perl hashbang in capr.pl Shankar, Murali
- Re: Alter Perl hashbang in capr.pl Ralph Lange
- Navigate by Date:
- Prev:
Re: Alter Perl hashbang in capr.pl Ralph Lange
- Next:
Re: Alter Perl hashbang in capr.pl Andrew Johnson
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Alter Perl hashbang in capr.pl Ralph Lange
- Next:
Re: Alter Perl hashbang in capr.pl Andrew Johnson
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|