Re: Use of %{__*} macros

[Chris Adams <cmadams hiwaay net>]

Once upon a time, Jeff Johnson <jbj@JBJ.ORG> said:
> FWIW, I'm not sure that spec files are any better off with
> 	%{__make}
> rather than
> 	make
> 
> You can almost always control for what make is executed with PATH, and,
> if not, there's something crazed in your build environment.

It can be a portability thing.  For example, on non-Linux systems, GNU
make is often installed as "gmake" instead of "make".  If the spec file
uses %{__make}, then I can just put "%define %__make gmake" in the
macros file.

I don't do this on my Tru64 setup with make (I installed GNU make as
"make"), but I do use it with %{__cc}.  I use the Compaq C compiler as
my first choice everywhere, so I "%define %__cc cc -I/usr/local/include"
and "%define %__cpp %{__cc} -E".  I also add

  CC="${CC:-%{__cc}}" ; export CC ; \

to the %configure macro (I need to bugzilla the __cpp and configure
changes when I get a chance, as they'd be good everywhere).  When I have
to use gcc (a few things assume gcc for no apparent good reason), I put

%define __cc gcc
%define __cpp gcc -E
%ifarch alpha
%define optflags -O2 -mieee
%else
%define optflags -O2
%endif

at the top of the .spec file.  This brings up a question I've had: is it
possible to put additional variables in the rpmrc file that would be
architecture specific?  For example, I'd like to have "optflags" have
the args for Compaq C and "gccoptflags" for GNU C.
-- 
Chris Adams <cmadams@hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.