From: Christian Ehrhardt <ehrhardt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Hollis Blanchard
<hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>,
"kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: how to get it as module ?
Date: Mon, 03 Sep 2007 07:54:36 +0200 [thread overview]
Message-ID: <46DBA19C.8000208@linux.vnet.ibm.com> (raw)
In-Reply-To: <1188493997.24040.19.camel@basalt>
Hollis Blanchard wrote:
> On Thu, 2007-08-30 at 13:25 +0200, Christian Ehrhardt wrote:
>
>> Hi Hollis,
>> I saw (and somehow I remembered something similar) that you build in
>> your code instead into a module. I assume that this has some
>> dependencies to your offset magic.
>> As far as I played around with it I was not able to get it build as
>> module in any way (the exceptions_44.s stuff) - please feel free to
>> enlighten me or let yourself time and talk with me about it e.g. on Monday.
>>
>
> I don't really care about building it as a loadable module at this
> point. I don't see why it wouldn't work though, so if you're having a
> problem you'll need to elaborate a little. What is the build error?
>
You are right it's no hasty issue at the moment - but maybe we should
disable the option to build as module until it's ready.
The build error when enabling module in config - Its the build process
of exceptions_44x.S - may only need some Makefile changes:
make[2]: *** No rule to make target `drivers/kvm/exceptions_44x.c',
needed by `drivers/kvm/exceptions_44x.o'. Stop.
make[1]: *** [drivers/kvm] Error 2
make: *** [drivers] Error 2
I'll elaborate it in detail once I need it ;-)
--
Grüsse / regards,
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization
+49 7031/16-3385
Ehrhardt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org
Ehrhardt-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org
IBM Deutschland Entwicklung GmbH
Vorsitzender des Aufsichtsrats: Johann Weihen
Geschäftsführung: Herbert Kircher
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
parent reply other threads:[~2007-09-03 5:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1188493997.24040.19.camel@basalt>]
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=46DBA19C.8000208@linux.vnet.ibm.com \
--to=ehrhardt-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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