From: Sam Ravnborg <sam@ravnborg.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: problem building in separate directory
Date: Thu, 19 Jan 2006 21:08:32 +0100 [thread overview]
Message-ID: <20060119200832.GF3557@mars.ravnborg.org> (raw)
In-Reply-To: <43CF82EE.76F0.0078.0@novell.com>
On Thu, Jan 19, 2006 at 12:15:42PM +0100, Jan Beulich wrote:
> Sam,
>
> beyond the problem reported in http://marc.theaimsgroup.com/?l=linux-kernel&m=113751198318080&w=2, I see another
> problem: There now is a .kernelrelease file getting generated in the source tree, making it impossible to build from a
> read-only one. Thus I don't think the patch suggested there is correct. Instead, arrangements must be made for the make
> to happen in the output tree instead. I didn't have time to come up with a patch for this, yet.
>
Hi Jan.
Both issues are now fixed, see patches I just sent out.
Sam
prev parent reply other threads:[~2006-01-19 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 11:15 problem building in separate directory Jan Beulich
2006-01-19 20:08 ` Sam Ravnborg [this message]
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=20060119200832.GF3557@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=JBeulich@novell.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox