From: Daniel Hecken <dh-LcvzS2Pvy/8X0D0ZMPkEVw@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: 1 Bug found for compiling on 32 Bit machine
Date: Mon, 21 May 2007 11:07:17 +0200 [thread overview]
Message-ID: <46516145.9020202@bahntechnik.de> (raw)
In-Reply-To: <4651588A.1050808-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Avi Kivity schrieb:
> Daniel Hecken wrote:
>> Hello,
>>
>> I have found an issue for compiling on 32 Bit machines in
>> v2.6.22-rc1-g1ab29f3.
>>
>> I'm not sure if I have set the #ifdef CONFIG_X86_64 at the right place.
>> Please have a look at it. With this patch v2.6.22-rc1-g1ab29f3 compiles
>> und runs fine.
>>
>>
>
> v2.6.22-rc1-170-ga6935db compiles fine here. Can you double-check?
>
The warnings are gone, but mine only compiles with my patch. gcc is
Version 3.4.6 included in Ubuntu Feisty.
(Intel Core 2 Duo running 32 Bit Ubuntu Feisty with kernel 2.6.20-15)
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-05-21 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 7:47 1 Bug found for compiling on 32 Bit machine Daniel Hecken
[not found] ` <46514E80.3080208-LcvzS2Pvy/8X0D0ZMPkEVw@public.gmane.org>
2007-05-21 8:30 ` Avi Kivity
[not found] ` <4651588A.1050808-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-05-21 9:07 ` Daniel Hecken [this message]
2007-05-23 11:40 ` Daniel Hecken
[not found] ` <4654281D.10806-LcvzS2Pvy/8X0D0ZMPkEVw@public.gmane.org>
2007-05-23 12:12 ` Avi Kivity
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=46516145.9020202@bahntechnik.de \
--to=dh-lcvzs2pvy/8x0d0zmpkevw@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@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 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.