From: Viallard Anthony <viallard@syscom-instruments.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] gcc: make sure we don't have a copy of libiberty.a in host library dir
Date: Tue, 04 Aug 2015 11:42:58 +0200 [thread overview]
Message-ID: <55C08922.4000600@syscom-instruments.com> (raw)
In-Reply-To: <55B64251.6010404@openwide.fr>
On 07/27/2015 04:38 PM, Romain Naour wrote:
>
> The --disable-install-libiberty option was broken, that's why the internal
> libiberty.a was installed in HOST_DIR.
>
> Hopefully, the same patch apply on gcc-4.7:
> http://patchwork.ozlabs.org/patch/500445/
>
> Care to test it ?
>
Hi Romain,
I tested the above patch but it doesn't work. The library 'libiberty.a'
is copied in 'output/host/usr/lib/'.
Maybe I missed somethings ?
I put the patch in the file
'package/gcc/4.7.4/920-fix-disable-install-libiberty-option.patch' and
add --disable-install-libiberty flag in HOST_GCC_COMMON_CONF_OPTS
variable of the gcc package.
----
diff --git a/package/gcc/gcc.mk b/package/gcc/gcc.mk
index be242cb..c23fe40 100644
--- a/package/gcc/gcc.mk
+++ b/package/gcc/gcc.mk
@@ -93,7 +93,8 @@ HOST_GCC_COMMON_CONF_OPTS = \
--with-gmp=$(HOST_DIR)/usr \
--with-mpfr=$(HOST_DIR)/usr \
--with-pkgversion="Buildroot $(BR2_VERSION_FULL)" \
- --with-bugurl="http://bugs.buildroot.net/"
+ --with-bugurl="http://bugs.buildroot.net/" \
+ --disable-install-libiberty
# Don't build documentation. It takes up extra space / build time,
# and sometimes needs specific makeinfo versions to work
----
and did the following command:
$ rm -rf output && make
I see the flag --disable-install-libiberty in my log so it seems to be
applied but the problem is always there.
Have you tried the patch on your side ?
Regards,
Anthony.
next prev parent reply other threads:[~2015-08-04 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 9:39 [Buildroot] [PATCH 1/1] gcc: make sure we don't have a copy of libiberty.a in host library dir Anthony Viallard
2015-07-27 14:38 ` Romain Naour
2015-08-04 9:42 ` Viallard Anthony [this message]
2015-08-04 9:54 ` Romain Naour
2015-08-04 11:30 ` Romain Naour
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=55C08922.4000600@syscom-instruments.com \
--to=viallard@syscom-instruments.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.