All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Numerous ARC related toolchain issues
Date: Fri, 10 Jun 2016 07:45:32 +0000	[thread overview]
Message-ID: <1465544685.2942.24.camel@synopsys.com> (raw)
In-Reply-To: <20160610093722.714b0240@free-electrons.com>

Hi Thomas,

On Fri, 2016-06-10 at 09:37 +0200, Thomas Petazzoni wrote:
> Hello,
> 
> On Fri, 10 Jun 2016 07:23:04 +0000, Alexey Brodkin wrote:
> 
> > 
> > > 
> > > http://autobuild.buildroot.net/results/d73/d732127d136bacc6bc17b742028691437df7f5f9/build-end.log
> > > BFD (GNU Binutils) 2.26.51.20160308 assertion fail elf32-arc.c:1566??
> > This is yet another manifestation of PIE invocation on ARC.
> > We'll need to disable usage of PIE in linuxpam.
>
> Ah, OK. Shouldn't gcc be modified on ARC to either ignore the pie flag,
> or alternatively bail out immediately with a clear error? At least it
> would be much more easy to analyze the error than a weird assertion
> failure down the road in the linker.

See PIE is a real requirement for U-Boot (because it relocates itself on early boot)
and for some reason U-Boot gets built with -PIE flag perfectly fine.

So we cannot just disable PIE support at least until U-Boot for ARC gets
auto-relocated. But for user-space apps indeed we don't support PIE still and
so existing code in toolchain fails here and there.

Funny enough that's better to see a failure during compilation compared to
silent segfault on attempt to run already built app. BTW now I can recall that exactly
this hit me with older toolchain - I needed wireshark so I built it flawlessly but
on execution dumpcap was segfaulting right on start. But being lazy enough I never
sent a patch to disable PIE in Wireshark :(

-Alexey

      reply	other threads:[~2016-06-10  7:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 15:50 [Buildroot] Numerous ARC related toolchain issues Thomas Petazzoni
2016-06-10  7:23 ` Alexey Brodkin
2016-06-10  7:37   ` Thomas Petazzoni
2016-06-10  7:45     ` Alexey Brodkin [this message]

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=1465544685.2942.24.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=buildroot@busybox.net \
    /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.