From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] package/gcc: comment on why we override the generic configure commands
Date: Sun, 22 Nov 2015 21:48:09 +0100 [thread overview]
Message-ID: <56522A09.2090200@mind.be> (raw)
In-Reply-To: <71e3b6c662031621f10fc3e1160ae1738204839b.1448202976.git.yann.morin.1998@free.fr>
On 22-11-15 15:39, Yann E. MORIN wrote:
> The explanations given in the commit log of 7d6c79 (Compile static
> versions of gcc libraries) do not explain why we have to provide custom
> configure commands, instead of just adding --enable-static to the
> configure options.
>
> Add a comment in the code that explains why that is so. Add a pointer to
> the ML archives with the explanations, too.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: J?r?me Pouiller <jezz@sysmic.org>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Regards,
Arnout
> ---
> package/gcc/gcc-final/gcc-final.mk | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/package/gcc/gcc-final/gcc-final.mk b/package/gcc/gcc-final/gcc-final.mk
> index 7802855..dbdb615 100644
> --- a/package/gcc/gcc-final/gcc-final.mk
> +++ b/package/gcc/gcc-final/gcc-final.mk
> @@ -27,6 +27,15 @@ HOST_GCC_FINAL_SUBDIR = build
>
> HOST_GCC_FINAL_PRE_CONFIGURE_HOOKS += HOST_GCC_CONFIGURE_SYMLINK
>
> +# We want to always build the static variants of all the gcc libraries,
> +# of which libstdc++, libgomp, libmudflap...
> +# To do so, we can not just pass --enable-static to override the generic
> +# --disable-static flag, otherwise gcc fails to build some of those
> +# libraries, see;
> +# http://lists.busybox.net/pipermail/buildroot/2013-October/080412.html
> +#
> +# So we must completely override the generic commands and provide our own.
> +#
> define HOST_GCC_FINAL_CONFIGURE_CMDS
> (cd $(HOST_GCC_FINAL_SRCDIR) && rm -rf config.cache; \
> $(HOST_CONFIGURE_OPTS) \
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-11-22 20:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 14:39 [Buildroot] [PATCH 0/3] core+gcc: align configure commands (branch yem/quickies-for-master) Yann E. MORIN
2015-11-22 14:39 ` [Buildroot] [PATCH 1/3] core/pkg-autotools: align host configure commands to target one Yann E. MORIN
2015-11-22 20:46 ` Arnout Vandecappelle
2015-11-23 17:38 ` Thomas Petazzoni
2015-11-23 17:51 ` Yann E. MORIN
2015-11-23 17:55 ` Yann E. MORIN
2015-11-23 20:09 ` Thomas Petazzoni
2015-11-23 20:51 ` Yann E. MORIN
2015-11-22 14:39 ` [Buildroot] [PATCH 2/3] package/gcc: comment on why we override the generic configure commands Yann E. MORIN
2015-11-22 15:11 ` Jérôme Pouiller
2015-11-22 20:48 ` Arnout Vandecappelle [this message]
2015-11-23 17:38 ` Thomas Petazzoni
2015-11-22 14:39 ` [Buildroot] [PATCH 3/3] package/gcc: align gcc-final configure-cmds to the generic ones Yann E. MORIN
2015-11-22 20:59 ` Arnout Vandecappelle
2015-11-22 21:02 ` Yann E. MORIN
2015-11-23 20:14 ` Thomas Petazzoni
2015-11-24 18:39 ` Yann E. MORIN
2015-12-29 22:06 ` Yann E. MORIN
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=56522A09.2090200@mind.be \
--to=arnout@mind.be \
--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