[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: unable to use $ORIGIN in rpath
From: |
Paul Smith |
Subject: |
RE: unable to use $ORIGIN in rpath |
Date: |
Wed, 15 Aug 2007 20:04:37 -0400 |
On Thu, 2007-08-16 at 00:03 +0100, Dave Korn wrote:
> Which still leaves me one curiosity: how come $(origin ...) reports
> 'environment' for "if-cpu" in the submakefile?
Whoops, sorry, I lied.
I checked the code again and if you explicit export a variable then make
will put it into the environment, regardless of the variable name. It's
only variables where you don't specify one way or the other that the
naming convention check is done.
--
-------------------------------------------------------------------------------
Paul D. Smith <address@hidden> Find some GNU make tips at:
http://www.gnu.org http://make.paulandlesley.org
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
- Re: unable to use $ORIGIN in rpath, (continued)
- 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, 2007/08/15
- RE: unable to use $ORIGIN in rpath,
Paul Smith <=
- Re: unable to use $ORIGIN in rpath, m c, 2007/08/17