Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gcc (arc): backport PR56780 patches
Date: Wed, 13 May 2015 20:48:10 +0000	[thread overview]
Message-ID: <1431550090.3047.11.camel@synopsys.com> (raw)
In-Reply-To: <1431380716-5176-1-git-send-email-romain.naour@openwide.fr>

Hi Romain,

On Mon, 2015-05-11 at 23:45 +0200, Romain Naour wrote:
> --disable-install-libiberty configure option is broken
> in gcc 4.8.x, so libiberty.a is always installed in HOST_DIR.
> 
> This library broke the host-gdb build due to a fpic/fPIC issue.
> 
> Note: host-binutils-arc-2014.12 install libiberty.a in HOST_DIR
> but it was overwritten by the gcc one. The host-binutils's
> libiberty.a also broke the host-gdb build. This should be
> fixed in a followup patch.
> 
> Signed-off-by: Romain Naour <romain.naour@openwide.fr>
> Cc: Alexey Brodkin <abrodkin@synopsys.com>
> ---
> Alexey, --disable-install-libiberty doesn't work
> for host-binutils-arc-2014.12. Can you have a look ?
> Thanks

Indeed our binutils are still based on 2.23 branch and corresponding
patches were missing.

What I did I just copied your "851-PR-other-56780.patch" to
"package/binutils/arc-2014.12" folder and on host-binutils rebuild no
libiberty.a was put in "host/usr/lib64".

Care to send another patch that adds "851-PR-other-56780.patch" to
"package/binutils/arc-2014.12" or should I do it myself?

-Alexey

  parent reply	other threads:[~2015-05-13 20:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 21:45 [Buildroot] [PATCH] package/gcc (arc): backport PR56780 patches Romain Naour
2015-05-11 22:19 ` Peter Korsgaard
2015-05-13 20:48 ` Alexey Brodkin [this message]
2015-05-13 21:18   ` Romain Naour
2015-05-13 21:19     ` Alexey Brodkin

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=1431550090.3047.11.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox