Re: Override... but not really

2010-08-09 Thread Philip Prindeville
On 8/9/10 6:07 PM, Paul Smith wrote: On Mon, 2010-08-09 at 14:00 -0700, Philip Prindeville wrote: The offender I'm staring at right now is ppp-2.4.5. I'll try to autoconfiscate it (autoconf + obsfucate?) later. I wasn't suggesting you should autoconfiscate it. I was suggesting the maintainer

Re: Override... but not really

2010-08-09 Thread Paul Smith
On Mon, 2010-08-09 at 14:00 -0700, Philip Prindeville wrote: > The offender I'm staring at right now is ppp-2.4.5. > > I'll try to autoconfiscate it (autoconf + obsfucate?) later. I wasn't suggesting you should autoconfiscate it. I was suggesting the maintainers of the package should. PPP is a

Re: Override... but not really

2010-08-09 Thread Philip Prindeville
On 8/9/10 1:46 PM, Paul Smith wrote: On Mon, 2010-08-09 at 12:41 -0700, Philip Prindeville wrote: Alas much of this is beyond my control, and it's not a single project: it's a Linux distro having a couple of hundred projects, many of which have several directories deep of makefile nesting. Ah,

Re: Override... but not really

2010-08-09 Thread Edward Welbourne
> I do a lot of cross-compilation, where the platform requires a set > of CFLAGS to always be present, such as -march=xxx and > -isysroot= ... Suggestion: Set CROSS = -march=xxx -isysroot=yyy where you're currently trying to hack CFLAGS and have makefiles that are actually going to use CFLAGS

Re: Override... but not really

2010-08-09 Thread Philip Prindeville
On 8/9/10 12:12 PM, Paul Smith wrote: On Mon, 2010-08-09 at 11:54 -0700, Philip Prindeville wrote: I guess I was thinking that variables are exported between makes the same way that environments variables are passed between processes. Well, certainly variables CAN be exported by make (see the

Re: Override... but not really

2010-08-09 Thread Paul Smith
On Mon, 2010-08-09 at 12:41 -0700, Philip Prindeville wrote: > Alas much of this is beyond my control, and it's not a single project: > it's a Linux distro having a couple of hundred projects, many of which > have several directories deep of makefile nesting. Ah, well, you didn't say so :-). One

Re: Override... but not really

2010-08-09 Thread Paul Smith
On Mon, 2010-08-09 at 11:54 -0700, Philip Prindeville wrote: > I guess I was thinking that variables are exported between makes the > same way that environments variables are passed between processes. Well, certainly variables CAN be exported by make (see the "export" command) and passed to sub-ma

Re: Override... but not really

2010-08-09 Thread Philip Prindeville
On 8/9/10 10:25 AM, Paul Smith wrote: On Mon, 2010-08-09 at 10:00 -0700, Philip Prindeville wrote: Is this expected behavior? Yes. $ cat makefile1 override CFLAGS+=-DB $(info makefile1: CFLAGS=$(CFLAGS)) all: make -f makefile2 $ cat makefile2 $(info makefile2: CFLAGS=$(CFLAGS)) overr

Re: Override... but not really

2010-08-09 Thread Philip Prindeville
Sorry, I sent that off and then realized that a little context might be more useful. I do a lot of cross-compilation, where the platform requires a set of CFLAGS to always be present, such as -march=xxx and -isysroot= ... The problem is that if you pass these in from the command line as "

Re: Override... but not really

2010-08-09 Thread Paul Smith
On Mon, 2010-08-09 at 10:00 -0700, Philip Prindeville wrote: > Is this expected behavior? Yes. > $ cat makefile1 > override CFLAGS+=-DB > $(info makefile1: CFLAGS=$(CFLAGS)) > all: > make -f makefile2 > $ cat makefile2 > $(info makefile2: CFLAGS=$(CFLAGS)) > override CFLAGS+=-DC > $(info m

Override... but not really

2010-08-09 Thread Philip Prindeville
Is this expected behavior? $ cat makefile1 override CFLAGS+=-DB $(info makefile1: CFLAGS=$(CFLAGS)) all: make -f makefile2 $ cat makefile2 $(info makefile2: CFLAGS=$(CFLAGS)) override CFLAGS+=-DC $(info makefile2: CFLAGS=$(CFLAGS)) all: @echo foo $ make -f makefile1 CFLAGS=