On Wed, Jan 23, 2002 at 09:33:17AM -0600, Chris Adams wrote:
> 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.
ITYM "%__make gmake"
> 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
CCC is sweet.
--
Need to sell some blood,
Just to make payments for you.
Please don't tell my wife.
-- O2 haiku in reputable.com
Attachment:
pgp00022.pgp
Description: PGP signature