On May 29, 2012, at 12:12 PM, Gordan Bobic wrote:

> On 05/29/2012 05:02 PM, Mardy Marshall wrote:
>> Hi All,
>> 
>> I know that this is not for the faint of heart, but
>> I'm interested in rebuilding the rootfs from the SRPM's.
> 
> You cannot rebuild the rootfs itself from source. You can rebuild it from the 
> binary RPMs, if that's what you actually mean - have a look here:
> 
> http://lists.redsleeve.org/pipermail/users/2012-May/000027.html
> 
> Specifically, the par that says:
> In a nutshell, I build it on an existing, working ARM machine in a
> chroot, using:
> 
> yum --installroot=/path/to/chroot install <list of basic rpms>
> 
> Then, force-re-install (rpm -Uvh --force --root=/path/to/chroot):
> - initscripts (or shutdown will hang due to one of the init scripts
> missing, haven't figured out why yet)
> - MAKEDEV (or you'll get start time complaints about vcsa user missing,
> again, don't know why the initial install doesn't add it)
> 
> If you really DO mean from source, you'll have to rebuild most of the 
> distribution binary rpms from src.rpms, and then install those binary rpms 
> using yum as described above.
> 
>> Are there any scripts or how-to notes that the RedSleeve team can share?
> 
> No scripts worth sharing. Since you can start from the existing RedSleeve 
> repository, you can use that to rebuild all the src.rpms in mock. Simply 
> iterate through all the packages until they are all built (this takes about a 
> month on a SheevaPlugs or two) and after each build copy the resulting rpms 
> from the mock/<chroot>/results directory somewhere out of the way. When you 
> are done, use createrepo to create the manifest, point the yum repository 
> path to your newly built folder, and use the above yum line.
> 
> Just out of interest, what's wrong with the RedSleeve rootfs as is? Any 
> particular reason why it doesn't work for you?
> 
> Gordan
> 

Unfortunately, yes, I am looking to rebuild the binary RPM's from their 
corresponding source RPM's and then build a new rootfs.  The reason for doing 
this is that for my particular target, I need to modify some of the ARM 
specific compilation options that the packages were originally compiled with.

To speed things up, I was also hoping to be able to cross-compile everything on 
an X86 host.

-Mardy

Reply via email to