From: Sam Ravnborg <sam@ravnborg.org>
To: Jay Cliburn <jacliburn@bellsouth.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Allow (O=...) from file
Date: Wed, 5 Dec 2007 22:00:03 +0100 [thread overview]
Message-ID: <20071205210003.GA15366@uranus.ravnborg.org> (raw)
In-Reply-To: <20071204210433.4d7ee66c@osprey.hogchain.net>
On Tue, Dec 04, 2007 at 09:04:33PM -0600, Jay Cliburn wrote:
> Sam,
>
> This piece of the top-level Makefile in current git causes an
> out-of-tree driver Makefile to fail.
>
> 101 ifdef O
> 102 ifeq ("$(origin O)", "command line")
> 103 KBUILD_OUTPUT := $(O)
> 104 endif
> 105 endif
>
> The out-of-tree driver Makefile contains an O=... directive that
> (correctly) does _not_ specify the kernel source dir, and apparently
> isn't overridden by the command line either. If in the above Makefile
> snippet I change "command line" to "file", my out-of-tree make
> succeeds. What do you think about allowing O= to come from a file in
> addition to the command line?
When you change "command line" to "file" you actually makes kbuild
ignore the O=... value which is why it succeeds.
The problem we solve with the error below is that in some case
the Makefile for the kernel were overwritten.
And I do not really understand why this does not happen in yours
and Erik's case.
Anyway - the right fix seems to detect that the two directories
are equal and then just ignore the O=... setting.
But I am lacking time atm to fix it - only sparsely working on
Linux the next few weeks.
Sam
next prev parent reply other threads:[~2007-12-05 20:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 3:04 Allow (O=...) from file Jay Cliburn
2007-12-05 20:02 ` Erik Mouw
2007-12-05 21:00 ` Sam Ravnborg [this message]
2007-12-05 21:37 ` Erik Mouw
2007-12-05 21:49 ` Erik Mouw
2007-12-06 3:31 ` Jay Cliburn
2007-12-06 21:38 ` Sam Ravnborg
2007-12-08 20:14 ` Sam Ravnborg
2007-12-09 0:25 ` Jay Cliburn
2007-12-06 14:57 ` Jan Engelhardt
2007-12-07 0:24 ` Jay Cliburn
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=20071205210003.GA15366@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jacliburn@bellsouth.net \
--cc=linux-kernel@vger.kernel.org \
/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.