On 12/11/16 14:59, Jacco Ligthart wrote:
Hi All,
I started building RedSleeve 7.3. There probably won't be a release
before Centos 7.3 is officially released. That said, I've got a fairly
decent set of rpms build by now. I did not test any on install yet
(other than dependencies for build)
To be able to sync the results to you, I need to cleanup some disk space
here.
@Gordon, could you stop syncing RSEL6 stuff? I'm not working on this any
more and don't expect to any time soon.
ACK. Removed all the EL6 related cronjobs. I'll try to make an effort to
tidy and deduplicate the packages in the EL6 tree so there is a clean
set for any future work anybody wants to undertake on it.
Speaking of which - any volunteers for future EL6 maintenance?
Probably this is a good time to start putting our changes on github.
I couldn't agree more. I already added you to the redsleeve-linux github
organization.
@Bjarne, can you tell how you do this? You have more experience with
this than I do.
Bjarne, what's your github account, so I can add you to the organization?
Over to the content side of the 7.3 build:
_Notable changes_
- glibc does no longer build out-of-the-box. It needed a little patch
- we need newer kernel-headers. I adjusted upstream's kernel package to
build only the headers.
- mesa-private-llvm probably cannot be updated on our CPU
- valgrind also cannot be updated
- I was finally able to update java-1.6.0 (I now know how to disable
ARM32JIT)
Did this ever work? I seem to recall having this problem since the very
first build. Initially it just didn't work at all, then in a later
release it tried to build with NEON support on armv5tel, but the gist of
it is that IIRC JIT always had to be disabled. :-(
_Stats_
442 packages are build without change
1 package is still building (libreoffice)
If you are building this against the standard repo, I could image up a
chroot and kick it off on the monster aarch64 box I have here. Last time
I checked LibreOffice builds single-threaded, not sure if that's been
fixed since, but building the whole thing in tmpfs ought to help for
sure. If it's already building you'll probably have it complete before I
can set this up (IIRC it takes about 20 hours on my Chromebook), but if
you get a FTBFS, we could speed up debugging by shortening the build time.
Gordan
_______________________________________________
users mailing list
[email protected]
https://lists.redsleeve.org/mailman/listinfo/users
