-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OPTEE build failure due to buildroot's incompatibility with glibc 2.33 #179
Comments
Hi @xiangmy, Have you worked on upgrading Buildroot and EDK2 already? Or have you just met these errors? If you have patches to propose please do and I will be glad to review them. Otherwise I can work on the upgrade. |
Hi @jforissier , I can clean up my changes and push them. Thanks, |
@xiangmy that would be very helpful, thanks! |
Hi @jforissier , Sorry for the late update. Upgrading the EDK2 is quite painful. I tried various of commits/tags, but they all failed at some warnings with
BTW, the QEMU was also broken with However, the major problem is how I should upgrade EDK2. Do you have any advice? In summary, I manage to upgrade the QEMU and Buildroot but need your adice in updagraing EDK2. Thanks, |
Hi @xiangmy, The latest EDK2 stable tag works for me, with one additional change in .repo/manifests $ git diff
diff --git a/qemu_v8.xml b/qemu_v8.xml
index 219ec3b..165771c 100644
--- a/qemu_v8.xml
+++ b/qemu_v8.xml
@@ -21,7 +21,7 @@
<!-- Misc gits -->
<project path="buildroot" name="buildroot/buildroot.git" revision="refs/tags/2020.08" clone-depth="1" />
- <project path="edk2" name="tianocore/edk2.git" revision="refs/tags/edk2-stable201905" sync-s="true" />
+ <project path="edk2" name="tianocore/edk2.git" revision="refs/tags/edk2-stable202102" sync-s="true" />
<project path="mbedtls" name="ARMmbed/mbedtls.git" revision="refs/tags/mbedtls-2.16.0" clone-depth="1" />
<project path="qemu" name="qemu/qemu.git" revision="refs/tags/v5.1.0" clone-depth="1" />
<project path="trusted-firmware-a" name="TF-A/trusted-firmware-a.git" revision="refs/tags/v2.3" clone-depth="1" remote="tfo" />
build $ git diff
diff --git a/qemu_v8.mk b/qemu_v8.mk
index dfc52d4..6934949 100644
--- a/qemu_v8.mk
+++ b/qemu_v8.mk
@@ -29,7 +29,7 @@ DEBUG ?= 1
TF_A_PATH ?= $(ROOT)/trusted-firmware-a
BINARIES_PATH ?= $(ROOT)/out/bin
EDK2_PATH ?= $(ROOT)/edk2
-EDK2_TOOLCHAIN ?= GCC49
+EDK2_TOOLCHAIN ?= GCC5
EDK2_ARCH ?= AARCH64
ifeq ($(DEBUG),1)
EDK2_BUILD ?= DEBUG |
Hi @jforissier , Thanks for your help! Would you mind helping me review #180 and OP-TEE/build#464? Thanks, |
I'm not sure if you noticed issues also with the toolchain. I got a new computer last week and did a setup from scratch. I get the impression that Arm have updated the toolchain package to comply with the expected toolchain string (i.e. in include vendor). Since the two of you are sorting out various build errors due to recent changes, you'll probably need this patch as well at some point. I.e., what I'm saying is that it could be worth re-try doing a full build from scratch, including |
@jbech-linaro isn't this addressed by https://github.com/OP-TEE/build/blob/3.12.0/toolchain.mk#L27? |
Hmm, it certainly looks like it does. It looks like I must have made some mistake on my end in that case. Checking the commit date when you added this, tells me that it's pretty old (>6 months), which makes me even more confused. I'll re-run it to cross check. |
Symlinks are there after a re-run, so ... sorry for noise (and thanks pointing to this). |
@jbech-linaro no worries ;-) |
Is there any progress on this issue? I have the same problem building under Arch. |
I'm on the 3.12.0 branch and |
Hi @bitwave It seems 3.12.0 doesn't contain this fix. You can try master/3.13.0. Thanks, |
I tried 3.13.0, now getting this:
|
Dear OPTEE group,
The
glibc 2.33
removed_STAT_VER
and the upstream buildroot has reflected this change (https://git.busybox.net/buildroot/commit/?id=f45925a951318e9e53bead80b363e004301adc6f). So, I'm wondering whether OPTEE wants to update the buildroot to2021.02
.PS: I've tested the build process with
qemu_v8.xml
on my branch: 89c5402. I also attach the log of my failed build.BTW, the edk2 is also incompatible with
python 3.9
. For instance,python 3.9
removedtostring()
andfromstring
, and this will cause errors while building (https://bugs.python.org/issue38916).Thanks,
Mingyuan
The text was updated successfully, but these errors were encountered: