From: Khem Raj <raj.khem@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 6/6] gcc: musl related fixes for unwinding, ppc/secure-plt and gthr
Date: Wed, 3 Feb 2016 08:38:50 -0800 [thread overview]
Message-ID: <852326EB-DC9D-4912-AF5D-6BB837745EBE@gmail.com> (raw)
In-Reply-To: <CAJTo0LbL72SbPTh22uJbRPq9G8PJRQ8Tf80bKbjYVZGBaY_kVw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1493 bytes --]
> On Feb 3, 2016, at 8:17 AM, Burton, Ross <ross.burton@intel.com> wrote:
>
>
> On 3 February 2016 at 06:27, Khem Raj <raj.khem@gmail.com <mailto:raj.khem@gmail.com>> wrote:
> These issues are fixing building gcc for target, ppc issue
> helps in fixing discrepency between gcc cmdline and linker cmdline
>
> This appears to break glibc builds for me:
is it with security flags enabled or disabled and which arch.
my builds all went ok. I will do a clean build without sstate to see
if I can reproduce your issue. May be its because I have gold linker enabled
I will check that independently here.
>
> | checking version of bison... 3.0.4, ok
> | checking for libc-friendly stddef.h... yes
> | checking whether we need to use -P to assemble .S files... no
> | checking for .set assembler directive... no
> | checking for assembler gnu_unique_object symbol type... yes
> | checking for .previous assembler directive... yes
> | checking for .protected and .hidden assembler directive... yes
> | checking whether __attribute__((visibility())) is supported... yes
> | checking linker support for protected data symbol... no
> | checking for broken __attribute__((visibility()))... no
> | checking for broken __attribute__((alias()))... no
> | checking whether to put _rtld_local into .sdata section... no
> | checking for .preinit_array/.init_array/.fini_array support... no
> | configure: error: Need linker with .init_array/.fini_array support.
>
> Ross
[-- Attachment #1.2: Type: text/html, Size: 3080 bytes --]
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2016-02-03 16:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 6:27 [PATCH 0/6] Fix issues when using security_flags on musl Khem Raj
2016-02-03 6:27 ` [PATCH 1/6] nss-myhostname: Fix build " Khem Raj
2016-02-03 6:27 ` [PATCH 2/6] gcc: Fix build on musl with -fstack-protector Khem Raj
2016-02-03 6:27 ` [PATCH 3/6] security_flags: Disable fstack-protector for gcc runtime libs Khem Raj
2016-02-03 6:27 ` [PATCH 4/6] security_flags: Replace -fstack-protector-all with -fstack-protector-strong Khem Raj
2016-02-03 6:27 ` [PATCH 5/6] gcc: Assume libssp and dl_iterate_phdr on musl Khem Raj
2016-02-03 6:27 ` [PATCH 6/6] gcc: musl related fixes for unwinding, ppc/secure-plt and gthr Khem Raj
2016-02-03 16:17 ` Burton, Ross
2016-02-03 16:38 ` Khem Raj [this message]
2016-02-03 16:40 ` Burton, Ross
2016-02-03 19:27 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2016-02-04 22:55 [PATCH 1/6] nss-myhostname: Fix build on musl Khem Raj
2016-02-04 22:54 ` [PATCH V2 0/6] Fix issues when using security_flags " Khem Raj
2016-02-04 22:55 ` [PATCH 6/6] gcc: musl related fixes for unwinding, ppc/secure-plt and gthr Khem Raj
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=852326EB-DC9D-4912-AF5D-6BB837745EBE@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox