From: "Burton, Ross" <ross.burton@intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] uninative: Add allow-shlib-undefined to BUILD_LDFLAGS and drop other workarounds
Date: Tue, 17 Apr 2018 21:52:14 +0100 [thread overview]
Message-ID: <CAJTo0LYwLeeR0y0x=PdYKCSdvi1hku5q_ixf77Te+bKqC_Lk_Q@mail.gmail.com> (raw)
In-Reply-To: <1523983449-32655-1-git-send-email-richard.purdie@linuxfoundation.org>
On 17 April 2018 at 17:44, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> We have a problem when for example, a glibc 2.27 based system builds some
> library like libpopt-native and puts it into sstate then it is reused
> on a pre glibc-2.27 system to build something which depends on popt like
> rpm-native. This results in an error like:
>
> recipe-sysroot-native/usr/lib/libpopt.so: undefined reference to `glob@GLIBC_2.27'
dbus-glib-native is failing on a few builders like this:
| /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm-lsb/build/build/tmp/work/x86_64-linux/dbus-glib-native/0.108-r0/build/dbus/.libs/lt-dbus-binding-tool:
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found
(required by /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm-lsb/build/build/tmp/work/x86_64-linux/dbus-glib-native/0.108-r0/recipe-sysroot-native/usr/lib/libexpat.so.1)
Using the host libc doesn't seem right surely?
Ross
next prev parent reply other threads:[~2018-04-17 20:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 16:44 [PATCH] uninative: Add allow-shlib-undefined to BUILD_LDFLAGS and drop other workarounds Richard Purdie
2018-04-17 19:15 ` Andre McCurdy
2018-04-18 7:49 ` Khem Raj
2018-04-18 11:38 ` Richard Purdie
2018-04-18 11:34 ` Richard Purdie
2018-04-17 20:52 ` Burton, Ross [this message]
2018-04-17 20:57 ` Burton, Ross
2018-04-18 17:58 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJTo0LYwLeeR0y0x=PdYKCSdvi1hku5q_ixf77Te+bKqC_Lk_Q@mail.gmail.com' \
--to=ross.burton@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.