From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-2124690 ] external modules dont support seperate linux output dir
Date: Tue, 06 Jul 2010 09:28:22 +0000 [thread overview]
Message-ID: <E1OW4Ry-0008JB-Eu@sfs-web-3.v29.ch3.sourceforge.com> (raw)
Bugs item #2124690, was opened at 2008-09-23 16:38
Message generated for change (Comment added) made by jessorensen
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2124690&group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: kernel
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Henning Schild (hensch)
Assigned to: Nobody/Anonymous (nobody)
Summary: external modules dont support seperate linux output dir
Initial Comment:
When the linux kernel was build with O= or KBUILD_OUTPUT one can not build the external kvm modules for it.
kernel/Makefile sets up LINUXINCLUDE in the wrong way
i attached a patch fixing the problem for kvm-75
----------------------------------------------------------------------
>Comment By: Jes Sorensen (jessorensen)
Date: 2010-07-06 11:28
Message:
Verified with Jan, this has been fixed in upstream for quite a while.
Closing
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2124690&group_id=180599
next reply other threads:[~2010-07-06 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 9:28 SourceForge.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-23 14:38 [ kvm-Bugs-2124690 ] external modules dont support seperate linux output dir SourceForge.net
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=E1OW4Ry-0008JB-Eu@sfs-web-3.v29.ch3.sourceforge.com \
--to=noreply@sourceforge.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;
as well as URLs for NNTP newsgroup(s).