Re: optflags problem

[Jeff Johnson <jbj redhat com>]

On Thu, May 02, 2002 at 11:56:07AM -0400, Matthew R. MacIntyre wrote:
> > 
> > Look setting CFLAGS appropriately is really pretty simple, people
> > have been doing it for years without any (ahem) assistance from rpm.
> 
> Ok, well, let's brainstorm then.  What is a good way for me to set the CFLAGS
> and friends variables for 700+ packages based on the architecture they are
> being built for without having to edit the spec file for every single package?
> 
> The only thing I've come up with so far is to create a custom rpmrc, override
> the optflags values, and run rpm with --rcfile=myfile.  Is there another way
> to do this so that the CFLAGS and such will be setup properly for the target
> architecture the package is being built for?
> 
> I just tried exporting CFLAGS, and rebuilding, so maybe I've answered my own question.
> So maybe I'm confused about what optflags is for then.  What is it for, if I'm
> not using it properly?
> 

Yup, CLAGS in the environment is honored.

optflags from rpm configuration is from a time honored concept of
"re-producible builds" when rpm's (and linux's and gcc's and ..)
world view was much simpler.

	1) not all package use the RPM_OPTFLAGS convention.
	2) there are two competing configuration mechanisms that obscure
	what is supoosed to happen.
	3) there are differences amongst packages from different vendors.
	4) etc

Basically setting up "reproducible builds" is far more complicated then
just chossing optflags.

> > > but this isn't working either.  Is this part of the same brokenness?  How do I
> > > go about making those optflags be used?
> > >
> > 
> > Why do you think that optflags has anything to do with rebuilding bar.src.rpm?
> 
> Because the optflags that it picks up are translated into RPM_OPT_FLAGS and
> CFLAGS, CXXFLAGS, etc in the build scripts.  Then the package is compiled
> using these flags.  What's wrong with this?
> 

You still have not described what your build problem is, or even identified
what package or arch is involved. Without that info, I can't begin to tell you
what to do.

73 de Jeff

-- 
Jeff Johnson	ARS N3NPQ
jbj@redhat.com (jbj@jbj.org)
Chapel Hill, NC