On 2015-04-24 17:18, Jacco Ligthart wrote: > On 04/24/2015 06:06 PM, Troy Dawson wrote: >> >> I wish I could say I had a nice way. It seems to be 90% of the work >> on 10% of the packages. >> For the most part, doing the build loop like you said works for alot >> of the packages. The majority of the packages that needed tweaking >> are the ones that RHEL7 has marked as x86_64 only. >> I will give this tip. Don't start on Fedora 20 for your build repo, >> or even use it partway through. I did that on my arm build and was >> delighted that so many package built. Then after a month I started >> checking dependencies on them. Hardly anything would install because >> of the crazy dependencies. I think libpng was the biggest issue. It >> wanted the version of libpng in Fedora 20, which was newer than the >> version in RHEL7. Had to rebuild the whole thing again. >> > Similarly, don't start with fedora18. Here the biggest issues are > libffi > and libtasn1 (iirc). > For RedSleeve 7.1 I did not build many of the x86_64 only stuff. Only > corosync and golang. All the rest is not really needed or rightfully > x86_64 only. > > For reference this is the overview of the issues encountered when > building for armv5tel: > http://www.mirrorservice.org/sites/ftp.redsleeve.org/pub/el7/7.1/RS7.1_issuelog.html > > If relevant, the patches I made should also be there, but the syncing > has not completed yet. > (the older patches for Redsleeve 7.0 are here: > http://www.mirrorservice.org/sites/ftp.redsleeve.org/pub/el7/alpha/patches/ > and here: > http://www.mirrorservice.org/sites/ftp.redsleeve.org/pub/el7/alpha-updates/patches/ > ) There, from The Man, himself - thanks for joining the thread. :) Gordan