From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next 1/4] support/gnuconfig: update to 2019-05-28
Date: Wed, 29 May 2019 08:57:02 +0200 [thread overview]
Message-ID: <20190529085702.22a67ca0@windsurf.home> (raw)
In-Reply-To: <33f72710-e524-fa9a-cd43-73a2e339da83@mind.be>
Hello,
On Tue, 28 May 2019 23:31:55 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> This variable is only used to pass --build arguments during configure, so we
> could use = instead of := and use the installed one from $(HOST_DIR).
>
> However, we can also completely remove it. There should never be any reason to
> pass --build to configure - especially if you're using *exactly* the same value
> as the default.
Yes: --build is autodetected by the configure script, by running
config.guess, and it will anyway be our config.guess, since we
overwrite the one provided by the package in a post-patch hook by our
config.guess.
> This was pulled in as part of a7e49eb2af which added 7000 lines
> of code. If there ever was any reason to do this, nobody remembers :-)
Indeed :)
> Note that we still need it for libnspr because that uses $host for build, so we
> have to override the --host given by the configure commands, so we need to know
> what --host should be. But there we can definitely use the downloaded and
> installed config.guess.
Right.
Thanks for the feedback, I'll try to follow-up with a proposal.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-29 6:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 8:29 [Buildroot] [PATCH next 0/4] Misc improvements to C-SKY support Thomas Petazzoni
2019-05-28 8:29 ` [Buildroot] [PATCH next 1/4] support/gnuconfig: update to 2019-05-28 Thomas Petazzoni
2019-05-28 9:32 ` Peter Korsgaard
2019-05-28 20:07 ` Thomas Petazzoni
2019-05-28 21:31 ` Arnout Vandecappelle
2019-05-29 6:57 ` Thomas Petazzoni [this message]
2019-05-28 8:29 ` [Buildroot] [PATCH next 2/4] toolchain/toolchain-external/toolchain-external-csky: new package Thomas Petazzoni
2019-05-28 8:29 ` [Buildroot] [PATCH next 3/4] configs/csky_gx6605s: use the C-SKY external toolchain package Thomas Petazzoni
2019-05-28 8:29 ` [Buildroot] [PATCH next 4/4] support/config-fragments/autobuild: add testing for the C-SKY architecture Thomas Petazzoni
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=20190529085702.22a67ca0@windsurf.home \
--to=thomas.petazzoni@bootlin.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