From: Robert Yang <liezhi.yang@windriver.com>
To: Khem Raj <raj.khem@gmail.com>, Ross Burton <ross.burton@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/8] e2fsprogs: 1.43 -> 1.43.1
Date: Mon, 25 Jul 2016 10:53:11 +0800 [thread overview]
Message-ID: <57957F17.9040603@windriver.com> (raw)
In-Reply-To: <CAMKF1soDrhTdO0hxNb3L_Op=QCG-QGpkiS5oz2_PxRL=CVxNFg@mail.gmail.com>
On 07/23/2016 04:44 AM, Khem Raj wrote:
> On Jul 22, 2016 12:52 PM, "Burton, Ross" <ross.burton@intel.com
> <mailto:ross.burton@intel.com>> wrote:
> >
> >
> > On 22 July 2016 at 09:47, Robert Yang <liezhi.yang@windriver.com
> <mailto:liezhi.yang@windriver.com>> wrote:
> >>
> >> Sorry, updated in the repo:
> >>
> >> git://git.openembedded.org/openembedded-core-contrib
> <http://git.openembedded.org/openembedded-core-contrib> rbt/pu
> >
> >
> > And now I notice that its failing on musl:
> >
> > | (cd elfshared; i586-poky-linux-musl-gcc -m32 -march=i586
> --sysroot=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-musl/build/build/tmp/sysroots/qemux86
> -o libcom_err.so.2.1 \
> > | -L../../../lib -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-z,relro
> -Wl,-z,now -fPIC -shared \
> > | -Wl,-soname,libcom_err.so.2 error_message.o et_name.o init_et.o com_err.o
> com_right.o )
> > | i586-poky-linux-musl-ar rc libcom_err.a error_message.o et_name.o init_et.o
> com_err.o com_right.o
> > | error_message.o: In function `init_debug':
> > | /usr/src/debug/e2fsprogs/1.43.1-r0/git/lib/et/error_message.c:260:
> undefined reference to `__stack_chk_fail_local'
> > | com_err.o: In function `default_com_err_proc':
> > | /usr/src/debug/e2fsprogs/1.43.1-r0/git/lib/et/com_err.c:63: undefined
> reference to `__stack_chk_fail_local'
> > | collect2: error: ld returned 1 exit status
> >
> > I guess the hardening needs to be glibc specific? (CC'ing Khem for an opinion).
>
> Musl work that have been done has been using hardening from day 1. So this
> should be fixed. Musl images work fine with pie
Hi Khem,
This happens on i586 (MACHINE=qemux86), the core2_64(MACHINE=qemux86-64) works
well. The failed option is -fstack-protector-strong, maybe something is wrong
with i586-musl-toolchain ?
// Robert
> >
> > Ross
>
next prev parent reply other threads:[~2016-07-25 2:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 13:43 [PATCH 0/8] Packages Upgrade Robert Yang
2016-07-19 13:44 ` [PATCH 1/8] e2fsprogs: 1.43 -> 1.43.1 Robert Yang
2016-07-21 21:40 ` Burton, Ross
2016-07-22 8:47 ` Robert Yang
2016-07-22 19:52 ` Burton, Ross
[not found] ` <CAMKF1spZ5qT2xfcyZtXKWYHk=6yiX0sQkWOpuOro_1ZAp_M=pQ@mail.gmail.com>
2016-07-22 20:44 ` Khem Raj
2016-07-25 2:53 ` Robert Yang [this message]
2016-07-19 13:44 ` [PATCH 2/8] git: 2.8.4 -> 2.9.2 Robert Yang
2016-07-19 13:44 ` [PATCH 3/8] guile: 2.0.11 -> 2.0.12 Robert Yang
2016-07-19 13:44 ` [PATCH 4/8] gnu-efi: 3.0.3 -> 3.0.4 Robert Yang
2016-07-19 13:44 ` [PATCH 5/8] slang: 2.2.4 -> 2.3.0 Robert Yang
2016-07-22 8:54 ` Burton, Ross
2016-07-25 7:19 ` Robert Yang
2016-07-19 13:44 ` [PATCH 6/8] gettext: 0.19.6 -> 0.19.8.1 Robert Yang
2016-07-19 16:37 ` Burton, Ross
2016-07-20 3:12 ` Robert Yang
2016-07-19 13:44 ` [PATCH 7/8] gettext-minimal-native: 0.19.4 " Robert Yang
2016-07-19 13:44 ` [PATCH 8/8] ccache: 3.2.4 -> 3.2.5 Robert Yang
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=57957F17.9040603@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=ross.burton@intel.com \
/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.