ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] [PATCH] Fix colilo build when using fully relocatable toolcha


From: Stuart Hughes
Subject: Re: [Ltib] [PATCH] Fix colilo build when using fully relocatable toolchains. : docu
Date: Fri, 08 Dec 2006 08:34:58 +0000

On Thu, 2006-12-07 at 13:32 -0500, Carlos O'Donell wrote:
> On Thu, Dec 07, 2006 at 03:24:28PM +0000, Stuart Hughes wrote:
> > Normally to make minor patches like this, you can run ./ltib -m
> > patchmerge (it looks like you did?).
> 
> I did this. It just happens that I attached the patch inline.
>  
> > That will create an actual patch-file and put it into <basedir>/pkgs.
> > You'll get a name like colilo-0.3.3-nnnnnnnn.patch.  The nnnn bit is
> > just a time in seconds since the epoch.  The idea is to make sure it's
> > likely to be unique as nothing ever gets replaced/modified in the GPP.
> > Also patchmerge will also update the colilo.spec file and add the new
> > patch in so that next time you build it will use the new patch.
> > 
> > Normally I re-name my patches to something more meaningful (after
> > checking it is unique) and I then change the reference in the spec file.
> > Having done all that you can then either:  send the patch and a cvs diff
> > to the mailing list (attachments work best for me, I never know how to
> > avoid whitespace mangling in email clients).  Alternatively, if you're
> > going to be actively working on LTIB and you want to be a developer,
> > after I've got some confidence, I'd add the person to the list of
> > developers.  This would mean they can upload directly to the GPP
> > (http://www.bitshrine.org/cgi-bin/gpp_upload.cgi ) and do their own CVS
> > commits.
> > 
> > For this particular case, I can check in the change if you like? Let me
> > know.
> 
> 1. Checkout ltib from cvs this time.
> 2. Redo the patch.
> 3. Send you a diff against the SPEC file.
> 4. Send you the new patch.
> 
> How does that sound? It might be a couple of days before I get to this.
> 
> I've also noticed that 'base_libs' is also non-functional due to our
> sysroot setup. It seems this was written with a particular toolchain in
> mind. I have patches for this aswell.
> 
> Cheers,
> Carlos.

Hi Carlos,

I look forward to the colilo patch, I'll get it put into the system when
I get it.

If you have a patch for base_libs, that'd be great.  base_libs got
updated on the 24th Nov merge out, so you may want to take a look now.
As you say, I based the stuff in there for CodeSourcery toolchains on
the particular ones we had, anything we can do support more are welcome.

Thanks, Stuart











reply via email to

[Prev in Thread] Current Thread [Next in Thread]