XMMS (was: Re: rawhide report: 20050405 changes)

[Kyrre Ness Sjobak]

tir, 05.04.2005 kl. 18.38 skrev Justin Conover:
> On Apr 5, 2005 10:01 AM, Dan Williams <dcbw at redhat.com> wrote:
> > On Tue, 2005-04-05 at 09:51 -0600, Justin Conover wrote:
> > > On Apr 5, 2005 9:30 AM, seth vidal <skvidal at phy.duke.edu> wrote:
> > > > On Tue, 2005-04-05 at 11:25 -0400, Jeff Spaleta wrote:
> > > > > On Apr 5, 2005 11:07 AM, Justin Conover <justin.conover at gmail.com> wrote:
> > > > > > What I don't understand is if you grab xmms from "extras" via cvs, it
> > > > > > wont build because it needs a gcc4.patch.  How was the rawhide build
> > > > > > system building these packages if they break when you grab the
> > > > > > src.rpm?
> > > > >
> > > > >
> > > > > the xmms in rawhide was actually quite old... i see no evidence that
> > > > > it was rebuilt with gcc4 yet.
> > > >
> > > > right, it wasn't.
> > > >
> > > > -sv
> > > >
> > > >
> > >
> > > Is there a wiki or anything that explains how the rawhide build system
> > > works?  Just for usefull info to me and maybe many others.  I just
> > > want to know how it all works.
> > 
> > The package will only break when you recompile it with gcc4.  So, for
> > xmms, it was last updated _before_ gcc4 was made the default compiler
> > for Fedora.  Therefore, if the maintainer were to rebuild it now, since
> > that gcc4 change, it would break and the maintainer would be forced to
> > update the package before it could get into rawhide.
> > 
> > Dan
> > 
> > 
> So if I use 
> 
> CC=gcc32 rpmbuild -ba xmms.spec

Isn't it:

CC=gcc32
export CC
rpmbuild

(i am typing from memory here...)