| 1 |
On Tue, 28 Jun 2011 15:04:00 -0400 |
| 2 |
Nathan Phillip Brink <binki@g.o> wrote: |
| 3 |
|
| 4 |
> On Tue, Jun 28, 2011 at 10:24:26PM +0400, Peter Volkov wrote: |
| 5 |
> > ?? ??????, 28/06/2011 ?? 12:23 -0400, Mike Frysinger ??????????: |
| 6 |
> > > On Tuesday, June 28, 2011 02:54:03 Micha?? G??rny wrote: |
| 7 |
> > > > emake CC="$(tc-getCC)" CFLAGS="${CFLAGS}"... |
| 8 |
> > > |
| 9 |
> > > this is easily dangerous when it comes to packages (and many do) |
| 10 |
> > > that append in the Makefile. specifying on the command line |
| 11 |
> > > blocks those while passing via env works fine. i'm not sure it's |
| 12 |
> > > appropriate to provide as an example. |
| 13 |
> > |
| 14 |
> > Hm, I'm not sure I understand what you are talking about here. |
| 15 |
> > Could you provide example? |
| 16 |
> |
| 17 |
> I think he's referring to somethine like: |
| 18 |
> |
| 19 |
> Makefile: |
| 20 |
> CFLAGS += `pkg-config --cflags libxml-2.0` |
| 21 |
> |
| 22 |
> which would work fine for: |
| 23 |
> emake |
| 24 |
> |
| 25 |
> but which would override the pkg-config flags if you do: |
| 26 |
> emake CFLAGS="${CFLAGS}" |
| 27 |
|
| 28 |
But is overriding really useful in this particular case? It seems |
| 29 |
rather irrelevant here. |
| 30 |
|
| 31 |
AFAIR you can pass 'emake CFLAGS+=sth' too but not sure about that. |
| 32 |
|
| 33 |
-- |
| 34 |
Best regards, |
| 35 |
Michał Górny |
Archives