| Summary: | "cannot make copy relocation for protected symbol" build errors with musl and ld-is-gold | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Ming Liu <liu.ming50> | ||||
| Component: | core | Assignee: | Khem Raj <raj.khem> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | Medium+ | CC: | meta.mr.watcher, meta.watcher, raj.khem, randy.macleod | ||||
| Version: | 2.4 | ||||||
| Target Milestone: | 2.4 M3 | ||||||
| Hardware: | BeagleBone | ||||||
| OS: | arm | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||
| Attachments: |
|
||||||
|
Description
Ming Liu
2017-06-16 11:47:55 UTC
More information, I also tested with the following scenarios: ... MACHINE = "genericx86-64" TCLIBC = "musl" DISTRO_FEATURES_append = " ld-is-gold" ... ... MACHINE = "beaglebone" TCLIBC = "glibc" DISTRO_FEATURES_append = " ld-is-gold" ... ... MACHINE = "genericx86-64" TCLIBC = "glibc" DISTRO_FEATURES_append = " ld-is-gold" ... bitbake core-image-minimal the issue did not show up with any of the above configs, so it only impacts arm + bfd linker? musl did not support lazy binding, which was added lately, however there could be issues. Although I would like you to try out the latest master where the latest musl is now in oe-core. And see if it still happens if so, I can work with community to narrow down the issue. Meanwhile the workaround patch you posted look fine to me. Hi, Khem: I just tried out the latest poky. In meta/recipes-core/musl/musl_git.bb: SRCREV = "a08910fc2cc739f631b75b2d09b8d72a0d64d285" it's the latest commit in musl as you said, but the issues are still there, I see same compiling errors as I tested last time. I am planning to retest my workaround patch against the latest poky and send it OE mail list, to see if there is any chance it can be merged as a temporary fix before you and musl community figure out a real fix. Can you test this patch please
diff --git a/meta/recipes-core/musl/musl_git.bb b/meta/recipes-core/musl/musl_git.bb
index 53a8ba196a..93e3535c8d 100644
--- a/meta/recipes-core/musl/musl_git.bb
+++ b/meta/recipes-core/musl/musl_git.bb
@@ -36,6 +36,7 @@ CONFIGUREOPTS = " \
--libdir=${libdir} \
--includedir=${includedir} \
--syslibdir=${base_libdir} \
+ --disable-visibility \
"
do_configure() {
Just tried applying this patch, but the error still could be observed, for instance: | /home/peter-liu/opensource/poky-upstream/build/tmp/work/cortexa8hf-neon-poky-linux-musleabi/m4/1.4.18-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-musleabi/../../libexec/arm-poky-linux-musleabi/gcc/arm-poky-linux-musleabi/7.1.0/ld: error: ../lib/libm4.a(progname.o): cannot make copy relocation for protected symbol 'program_invocation_name', defined in /home/peter-liu/opensource/poky-upstream/build/tmp/work/cortexa8hf-neon-poky-linux-musleabi/m4/1.4.18-r0/recipe-sysroot/usr/lib/libc.so | collect2: error: ld returned 1 exit status | Makefile:1554: recipe for target 'm4' failed I think I gave you converse. Can you try --enable-visibility instead? Hi, Khem:
Just tried, still no lucky, I got the same error with:
diff --git a/meta/recipes-core/musl/musl_git.bb b/meta/recipes-core/musl/musl_git.bb
index 31583de..a047ac6 100644
--- a/meta/recipes-core/musl/musl_git.bb
+++ b/meta/recipes-core/musl/musl_git.bb
@@ -35,6 +35,7 @@ CONFIGUREOPTS = " \
--libdir=${libdir} \
--includedir=${includedir} \
--syslibdir=${base_libdir} \
+ --enable-visibility \
"
(In reply to comment #6) > I think I gave you converse. Can you try > > --enable-visibility > > instead? try --disable-visibility and --enable-visibility one by one btw you should use bitbake -ccleansstate musl m4 bitbake m4 Hi, Khem: That exactly is what I have done. > Hi, Khem:
> That exactly is what I have done.
Sorry, I just realized, I probably forgot to cleansstate when I was trying "--disable-visibility", will re-test that option.
I did cleansstate when trying "--enable-visibility" by the way.
Hi, Khem: The problem seems resolved with your suggestion "--disable-visibility" if I run cleansstate musl beforehand, now I have built core-image-minimal successfully. But I would like to try to build from scratch one more time. I am curious about the "cleansstate" thing, I do not understand why that is necessary? Since the CONFIGUREOPTS change will taint the do_configure hence will lead musl recompile, isn't that correct? If cleansstate is needed, does this mean the users would still get this problem even with your patch applied if they do not build from scratch? Just tried build core-image-minimal from scratch with:
diff --git a/meta/recipes-core/musl/musl_git.bb b/meta/recipes-core/musl/musl_git.bb
index 53a8ba196a..93e3535c8d 100644
--- a/meta/recipes-core/musl/musl_git.bb
+++ b/meta/recipes-core/musl/musl_git.bb
@@ -36,6 +36,7 @@ CONFIGUREOPTS = " \
--libdir=${libdir} \
--includedir=${includedir} \
--syslibdir=${base_libdir} \
+ --disable-visibility \
"
the problem seems fixed.
This is fixed by oe-core/5490efb7446196dce6a4be678263e8a73648446a |