On 13/11/16 01:30, Jacco Ligthart wrote:
_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.
Previous version took 15 hours on the Odroid U3. It does now build multi
threaded. I wonder how much time version 5 will cost in stead of
previous version 4. The build is now already running for a few hours.
Let it run for now.
Maybe I should build i on the Odroid XU4. then I should get eight core
performance :) Or maybe I get out-of-memory again.
That really is the best bit about this monster aarch64 motherboard I
have - I have 128GB of ECC RAM in it. :)
How do you build on the monster aarch64 box? I got an Odroid C2, which
is also aarch64. I managed to build and package their kernel using
CentOS aarch64. I even can make an Redsleeve image for it.
I don't think you can use the CentOS 7 kernel asd provided with a 32-bit
userspace, either CentOS 7 armv7hl or RSEL7 armv5tel due to page size
incompatibility. Somebody at RH decided to have their aarch64 build use
64KB memory pages, and 32-bit ARM userspace expects and is only capable
of 4KB memory pages, and this binaries segfault immediately. I am happy
to share the kernel config I use on my aarch64 box, which uses 4KB
memory pages. 64-bit userspace works fine with 4KB pages, but 32-bit
userspace doesn't work at all with 64KB pages.
I had a discussion on the CentOS aarch64 mailing list and got nowhere.
I'm sure you can find it in the CentOS arm-dev archives.
However, the
few times I tried to build something on it, the build always failed. The
build process detects an 64 bit CPU, tries to build for 64 bits and then
finds that the compiler is not able to do that.
I haven't used it extensively (as in for rebuilding a whole distro), but
the following worked for the few packages that I tried:
# echo armv5tel-redhat-linux > /etc/rpm/platform
That _should_ override platform/CPU detection provided the source
package's build script behaves properly. Mileage will vary with the
quality of the source package.
Gordan
_______________________________________________
users mailing list
[email protected]
https://lists.redsleeve.org/mailman/listinfo/users
