[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: unable to use $ORIGIN in rpath
From: |
Dave Korn |
Subject: |
RE: unable to use $ORIGIN in rpath |
Date: |
Thu, 16 Aug 2007 00:03:02 +0100 |
On 15 August 2007 19:41, Paul Smith wrote:
> On Wed, 2007-08-15 at 18:02 +0100, Dave Korn wrote:
>
>> I think I just ran across a similar situation, but I'm not sure it's the
>> exact same. I define a function in an include file:
>
> This is a different problem.
>
>> export if-cpu
>
> This statement is a no-op. Shell variable names must match the RE
> [a-zA-Z_][a-zA-Z0-9_]*, so it's illegal for make to export a make
> variable "if-cpu", containing a dash which is an illegal character in a
> shell's variable name, into the environment. Make will ignore all
> variables that don't have a valid shell variable name when it exports.
Which still leaves me one curiosity: how come $(origin ...) reports
'environment' for "if-cpu" in the submakefile?
cheers,
DaveK
--
Can't think of a witty .sigline today....
- Re: unable to use $ORIGIN in rpath, (continued)
- Re: unable to use $ORIGIN in rpath, m c, 2007/08/15
- Re: unable to use $ORIGIN in rpath, Paul Smith, 2007/08/15
- Re: unable to use $ORIGIN in rpath, m c, 2007/08/15
- Re: unable to use $ORIGIN in rpath, Paul Smith, 2007/08/15
- Re: unable to use $ORIGIN in rpath, m c, 2007/08/15
- Re: unable to use $ORIGIN in rpath, Paul Smith, 2007/08/15
- RE: unable to use $ORIGIN in rpath, Dave Korn, 2007/08/15
- RE: unable to use $ORIGIN in rpath, Paul Smith, 2007/08/15
- RE: unable to use $ORIGIN in rpath, Dave Korn, 2007/08/15
- RE: unable to use $ORIGIN in rpath, Dave Korn, 2007/08/16
- RE: unable to use $ORIGIN in rpath,
Dave Korn <=
- RE: unable to use $ORIGIN in rpath, Paul Smith, 2007/08/15
- Re: unable to use $ORIGIN in rpath, m c, 2007/08/17