Mailinglist Archive: opensuse-buildservice (166 mails)

< Previous Next >
[opensuse-buildservice] Failing to boot strap glibc for ARM on KVM workers
  • From: "Dominig ar Foll (Intel OTC)" <dominig.arfoll@xxxxxxxxx>
  • Date: Wed, 21 May 2014 11:03:22 +0200
  • Message-id: <537C6BDA.8050508@fridu.net>
Hello,

In the Tizen project are facing some difficulties in re-boot strapping Tizen3 Common for ARM.
We did an initial bootstrap using Tizen2 Mobile (a legacy Tizen 2 ARM based and that has allowed us to build almost all Tizen3 Common packages (only 8 out of 738 are still not building).

But now in order to get a clean built, we want to self-re-bootstrap the ARMrepoand we are facing difficulties with glibcand a few other packages.
We would need help to fix the glibc build issue first as we expect that the same fix will work for the other packages.
Our configuration uses OBS workers with KVM.

Our build issue can be seen here:
https://build.tizen.org/package/live_build_log?arch=armv7l&package=glibc&project=Tizen%3ACommon&repository=arm-wayland <https://build.tizen.org/package/live_build_log?arch=armv7l&package=glibc&project=Tizen%3ACommon&repository=arm-wayland>

The error is very strange:
/home/abuild/rpmbuild/BUILD/glibc-2.18/cc-base/iconv/iconvconfig: error while loading shared libraries: /home/abuild/rpmbuild/BUILD/glibc-2.18/cc-base/iconv/iconvconfig: failed to map segment from shared object: Operation not permitted

We think that the error is due to a package that is missing in a alternative architecture (e.g. IA32) during the boot strap process and the sharelib load fails due to the Arch mismatch but we might be wrong.
We have no clue on how to correct the issue.

Do you have any idea how to remove that lock ?
Does someone know how to bootstrap ARM on an OBS with KVM workers ?

Thanks in advance for your help.

--
Dominig ar Foll
Senior Software Architect
Open Source Technology Centre
Intel SSG

--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >