Re: [PATCH trace-cmd 3/3] Revert "trace-cmd: Use conditionalassignment of CC and AR"
From: Steven Rostedt
Date: Thu Mar 10 2011 - 08:07:48 EST
On Wed, 2011-03-09 at 22:41 -0800, Darren Hart wrote:
> On 03/09/2011 07:26 PM, Steven Rostedt wrote:
> > On Wed, 2011-03-09 at 21:51 -0500, Steven Rostedt wrote:
> >
> >> I'll play with some other make tricks and see if I can come up with a
> >> better solution.
> >
> > OK, it didn't take me long to come up with "Makefiles suck" ;)
>
> Yeah, that little tidbit I sent took longer to come up with than it
> should have :/
>
> >
> > But I did come up with a solution:
> >
> > ifneq ("$(origin CC)", "environment")
> > CC = gcc
> > endif
> >
> > CC := $(CROSS_COMPILE)$(CC)
>
> Why do we want to force CC=gcc? Isn't the right thing to make your OS
> setup cc to point to your preferred compiler since it is known to be the
> default for make?
Why not? The kernel does it. And yes, as I am following the kernel with
trace-cmd than other user space tools.
>
> On Ubuntu, cc -> gcc
> On Fedora 13, cc -> ccache
Ug, thanks for telling me. /me goes to disable ccache from his F13
installs.
>
> seems strange to force it to be gcc when users/distros have gone through
> the trouble to set it up on their system.
If you define CC as a environment variable, it will work with the other
solution.
>
>
> > This wont let make CC=xx work unless I also add a:
> >
> > ifneq ("$(origin CC)", "command line")
> >
> > around the above if, but do we care?
> >
>
> This starts to get to the point where others looking at it will choke on
> the expert Makefile usage.
>
Yeah, that took a bit of searching. Makefiles are far from being
obvious. But as you all know, I work in the world of obfuscation.
Probably why I prefer perl over python ;)
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/