From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] make: drop gnumake/gmake aliases for host-make
Date: Mon, 19 Nov 2018 15:02:27 +0100 [thread overview]
Message-ID: <20181119140228.19937-2-peter@korsgaard.com> (raw)
In-Reply-To: <20181119140228.19937-1-peter@korsgaard.com>
Now that glibc no longer checks for gnumake / gmake, these aliases can be
removed.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
package/make/make.mk | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/package/make/make.mk b/package/make/make.mk
index 790391c76e..1471576850 100644
--- a/package/make/make.mk
+++ b/package/make/make.mk
@@ -23,15 +23,5 @@ endif
HOST_MAKE_DEPENDENCIES = host-pkgconf
HOST_MAKE_CONF_OPTS = --without-guile
-# Some packages, like glibc, are looking for gnumake or gmake before
-# make program.
-# Create these symlink to use make binary generated by Buildroot for
-# the host.
-define HOST_MAKE_INSTALL_GNUMAKE
- ln -fs make $(HOST_DIR)/bin/gnumake
- ln -fs make $(HOST_DIR)/bin/gmake
-endef
-HOST_MAKE_POST_INSTALL_HOOKS += HOST_MAKE_INSTALL_GNUMAKE
-
$(eval $(autotools-package))
$(eval $(host-autotools-package))
--
2.11.0
next prev parent reply other threads:[~2018-11-19 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 14:02 [Buildroot] [PATCH 1/3] glibc: ensure BR2_MAKE is also used for subdirs Peter Korsgaard
2018-11-19 14:02 ` Peter Korsgaard [this message]
2018-11-19 14:02 ` [Buildroot] [PATCH 3/3] make: install host-make as host-make Peter Korsgaard
2018-11-19 14:35 ` yann.morin at orange.com
2018-11-19 14:56 ` Peter Korsgaard
2018-11-19 14:09 ` [Buildroot] [PATCH 1/3] glibc: ensure BR2_MAKE is also used for subdirs Baruch Siach
2018-11-19 14:27 ` Peter Korsgaard
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=20181119140228.19937-2-peter@korsgaard.com \
--to=peter@korsgaard.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.