From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] package/make: add host variant
Date: Tue, 4 Sep 2018 10:27:57 +0200 [thread overview]
Message-ID: <20180904102757.7ab08189@windsurf> (raw)
In-Reply-To: <CANQCQpbQwbKOpVA3rUE1jR18Breh8uZR1uRdizCo0F9RR1_C5g@mail.gmail.com>
Hello,
On Mon, 3 Sep 2018 14:55:11 -0500, Matthew Weber wrote:
> I plan to give this a test tomorrow. We have been close to sending
> something similar because of a Make 3 vs 4 issue across vintages of
> builds we've been supporting. I wonder if there is any interest
> picking this one back into the LTS?
If you're talking about the issue that Sam Voss was discussing on IRC,
then it's different. Your issue was that your host machine is using
make >= 4.0, but some of your funky packages don't like that and would
need make < 4.0 to build.
This is not handled by Romain's series@all, which handles the
opposite situation: packages that need make >= 4.0, but the host has
make < 4.0.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-04 8:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 19:19 [Buildroot] [PATCH v2 1/3] package/make: add host variant Romain Naour
2018-09-03 19:19 ` [Buildroot] [PATCH v2 2/3] dependencies: host-make version check Romain Naour
2018-09-04 0:10 ` Cam Hutchison
2018-09-05 1:39 ` Matthew Weber
2018-09-08 21:37 ` Thomas Petazzoni
2018-09-03 19:19 ` [Buildroot] [PATCH v2 3/3] package/glibc: allow to specify host-make Romain Naour
2018-09-05 1:40 ` Matthew Weber
2018-09-08 21:38 ` Thomas Petazzoni
2018-09-03 19:55 ` [Buildroot] [PATCH v2 1/3] package/make: add host variant Matthew Weber
2018-09-03 21:35 ` Arnout Vandecappelle
2018-09-04 8:27 ` Thomas Petazzoni [this message]
2018-09-04 13:44 ` Matthew Weber
2018-09-05 1:39 ` Matthew Weber
2018-09-08 21:37 ` 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=20180904102757.7ab08189@windsurf \
--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