[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The right way to use standard variable in

From: Thomas Dickey
Subject: Re: The right way to use standard variable in
Date: Thu, 2 Apr 2015 20:16:11 -0400 (EDT)

----- Original Message -----
| From: "Andy Falanga (afalanga)" <address@hidden>
| To: address@hidden
| Sent: Thursday, April 2, 2015 7:04:48 PM
| Subject: The right way to use standard variable in
| Hi,
| I placed the following in my file:
| because I found that as an example on a webpage someplace.  I
| reviewed so many learning about the autotools that I don't recall
| which one now.  I did this because there were some preprocessor
| flags that I wanted to have common to all sub-makefiles.
| I ran into a problem today, however, where I needed to add a -I
| directive to my CPPFLAGS in order to find the necessary headers.
|  Then, the problem stepped in.  Because I placed this line in
|, it was transcribed, verbatim (as it should), into
| configure.  The net result: not matter what I placed on the command
| line was ignored.  For example, the following:
| CPPFLAGS=-I/path/to/the/alternate/location ./configure
| --build=x86_64-linux --host=arm-poky-linux-gnueabi
| The additional path wasn't being appended, it was being stomped.  Did
| I miss a macro?  How should this be done because, obviously, I've
| gotten it incorrect.

changing that to

 ./configure --build=x86_64-linux --host=arm-poky-linux-gnueabi 

is likely to get the expected result

Thomas E. Dickey <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]