This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: the mechanics of unpacking the source for a toolchain

On Mon, 29 Sep 2003, Dan Kegel wrote:

> Robert P. J. Day wrote:
 
> >   but what about any of those components already existing in 
> > an exploded directory (good example -- kernel source.)  what do 
> > you do then?
> 
> Assume it's already patched.  This will be the case if
> you're using CVS, say.  Any patches you still need,
> you should apply to your local tree (and scream bloody
> murder until they make it into the CVS tree :-)

wait a minute.  so if one of the source variables points, not to
a tarball, but to an actual directory, you should assume that
directory has already been patched?  why?  i'm not disagreeing,
it's just not clear to me why you'd take this position.

rday


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]