From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/project
Date: Fri, 26 Sep 2008 07:04:09 -0700 (PDT) [thread overview]
Message-ID: <20080926140409.17D7E3C368@busybox.net> (raw)
Author: jacmet
Date: 2008-09-26 07:04:08 -0700 (Fri, 26 Sep 2008)
New Revision: 23518
Log:
project/Makefile.in: workaround issue with out-of-tree builds
Other packages might also support Linux-style out of tree builds
with the O=<dir> syntax (E.G. Busybox does). As make automatically
forwards command line variable definitions those packages get very
confused. Fix this by telling make to not do so
Modified:
trunk/buildroot/project/Makefile.in
Changeset:
Modified: trunk/buildroot/project/Makefile.in
===================================================================
--- trunk/buildroot/project/Makefile.in 2008-09-26 14:00:26 UTC (rev 23517)
+++ trunk/buildroot/project/Makefile.in 2008-09-26 14:04:08 UTC (rev 23518)
@@ -32,6 +32,12 @@
ifeq ("$(origin O)", "command line")
BASE_DIR := $(shell mkdir -p $(O) && cd $(O) && pwd)
$(if $(BASE_DIR),, $(error output directory "$(O)" does not exist))
+
+# other packages might also support Linux-style out of tree builds
+# with the O=<dir> syntax (E.G. Busybox does). As make automatically
+# forwards command line variable definitions those packages get very
+# confused. Fix this by telling make to not do so
+MAKEOVERRIDES =
endif
endif
next reply other threads:[~2008-09-26 14:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 14:04 jacmet at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-15 14:50 [Buildroot] svn commit: trunk/buildroot/project jacmet at uclibc.org
2009-01-06 23:38 ulf at uclibc.org
2008-09-16 20:53 jacmet at uclibc.org
2007-10-30 20:14 ulf at uclibc.org
2007-09-23 10:16 ulf at uclibc.org
2007-09-19 20:24 aldot at uclibc.org
2007-09-17 13:17 ulf at uclibc.org
2007-09-17 12:43 ulf at uclibc.org
2007-09-17 13:10 ` Bernhard Fischer
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=20080926140409.17D7E3C368@busybox.net \
--to=jacmet@uclibc.org \
--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