On 05-09-15 10:32, Gordan Bobic wrote: > On 05/09/15 09:25, Jacco Ligthart wrote: >> >>>> packages that I could not update: >>>> ==================== >>>> xulrunner-17.0.8-3.el6.0.src.rpm >>> >>> I'm pretty sure this is deprecated - it has been un-separated from the >>> firefox package. >> I know FF and TB don't need it any more, I did however need it to build >> PackageKit, icedtea-web and libproxy. > > Won't this build against the firefox package? Or does the last > buildable ff have separate xulruner? You build the last FF, but it dous not seem to have a build requirement for xulrunner. I think it's a lot of work, for linking to an known outdated version of FF. More important at this point is to get FF and TB to build. can you share how you fixed the gcc 4.8.2 inside the FF and TB packages?
>>>> Packages added: >>>> ========== >>>> google-crosextra-caladea-fonts-1.002-0.3.20130214.el6.1 >>>> google-crosextra-carlito-fonts-1.103-0.1.20130920.el6.1 >>>> json-c-0.11-12.el6 >>>> libgovirt-0.3.2-1.el6 >>>> numactl-2.0.9-2.el6.0 >>> >>> I'm pretty sure this is x86 specific. What depends on it? Is there a >>> configuration option to disable this dependency? >> irqbalance depends on it. >> I'm not sure it's x86 specific. I found the patch here: >> https://wiki.linaro.org/LEG/Engineering/Kernel/NUMA >> here it says: >> "There aren't any ARM NUMA systems out at the moment, but one can use >> the Linux NUMA subsystem to group cores that share an L2 cache together >> into the same node. For certain workloads this can then result in a >> decrease in the accesses to main memory." >> I guess we can argue both ways :) > > Fair enough, if it works. :) > >>>> packages available upstream but not build: >>>> ========================== >>> <SNIP> >>>> eclipse-3.6.1-6.13.el6 >>>> eclipse-birt-2.6.0-1.1.el6 >>>> eclipse-callgraph-0.6.1-1.el6 >>>> eclipse-cdt-7.0.1-4.el6 >>>> eclipse-changelog-2.7.0-1.el6 >>>> eclipse-dtp-1.8.1-1.1.el6 >>>> eclipse-emf-2.6.0-1.el6 >>>> eclipse-gef-3.6.1-3.el6 >>>> eclipse-linuxprofilingframework-0.6.1-1.el6 >>>> eclipse-mylyn-3.4.2-9.el6 >>>> eclipse-nls-3.6.0.v20120721114722-2.el6 >>>> eclipse-oprofile-0.6.1-1.el6 >>>> eclipse-rpm-editor-0.5.0-2.el6 >>>> eclipse-rse-3.2-1.el6 >>>> eclipse-subclipse-1.6.5-6.el6 >>>> eclipse-valgrind-0.6.1-1.el6 >>> >>> I never did get to the bottom why eclipse wasn't building. It took so >>> long to build that I eventually gave up because it meant waiting days >>> to see if each change I made resulted in a small amount of progress. >>> :( It may be less painful on an 8-core machine with 4GB of RAM, but on >>> a SheevaPlug (1.2GHz single core with 512MB of RAM) it wasn't really >>> workable. >> I tried a little. It's difficult, because it depends on itself. I could >> not get it to bootstrap after some reasonable attempts, went to google >> and found your unanswered questions in various mailinglists :) > > I think we can leave it for now - now ARM machine has enough RAM to > run eclipse anyway. :) > >>>> foghorn-0.1.2-1.el6 >>>> gcc-libraries-5.0.0-1.1.1.el6 >>>> gdisk-0.8.10-1.el6 >>>> gnu-efi-3.0g-2.el6 >>>> gprolog-1.3.1-6.el6 >>>> gpxe-0.9.7-6.14.el6 >>>> grub-0.97-94.el6 >>>> haproxy-1.5.4-2.el6 >>> >>> It surprises me that something as trivial as haproxy didn't build. Do >>> you have a build log? >> No, because I didn't try :) >> Until now I only updated packages that were previously in RSEL6. How do >> we go from here? cherry picking? or just try and build them all and see >> what happens? > > A mass build sounds like a good place to start. See what just works. > Cherry pick from the FTBFS if we need to. :) > Allright, I'll get back with the results Jacco _______________________________________________ users mailing list [email protected] http://lists.redsleeve.org/mailman/listinfo/users
