On Wed, 18 Oct 2006, Bogdan Costescu wrote:
On Wed, 18 Oct 2006, Dag Wieers wrote:
I was wondering if anyone knows of a better solution than explained in the valgrind FAQ, or better than upgrading make.
You mean that you want/need to have CFLAGS set when starting the build ? What's the reason for that ?
One of the packaging policies is that CFLAGS is set to match %{optflags} as part of the %build phase. %configure does that.
I'm able to build the latest RF mplayer SRPM (1.0-0.20.pre7.rf) on a CentOS 3.8 without this error. This is a real machine, not a VM, chroot or x86_64 one compiling for i386; building as a normal user, not as root. CFLAGS is not set when the rpmbuild command is started.
Neither is it when I start rpmbuild :)
So is this caused by a more recent configure/autotools used by the developers ?
Could you please explain how you envision a different configure/autotools changing the picture ?
I meant a different make/autotools. I prefer not to change my build environment. My packages should be able to build on the original distribution, not original distribution + new make/autotools.
I prefer not to deviate from Red Hat. I prefer not to replace Red Hat's make/autotools. For unmaintained distributions like RH7 or RH9 I couldn't care, but for EL2.1 and EL3 this is very much a liability.
Kind regards, -- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]