From: Benoit Rouits <brouits@free.fr>
To: Glynn Clements <glynn@gclements.plus.com>
Cc: "Kirkwood, David A." <DAVID.A.KIRKWOOD@saic.com>,
linux-admin@vger.kernel.org
Subject: Re: FW: 64 bit or 32 bit
Date: Tue, 21 Aug 2007 01:30:49 +0200 [thread overview]
Message-ID: <1187652649.24972.2.camel@localhost> (raw)
In-Reply-To: <18121.57145.907803.72926@cerise.gclements.plus.com>
Le lundi 20 août 2007 à 19:36 +0100, Glynn Clements a écrit :
> Benoit Rouits wrote:
>
> > > How can I tell if a given system is running a 32bit krnel or a 64bit
> > > kernel. I a system capable of running either, but I cannot figure
> > > out which kernel is installed on it.
> >
> > just make a C program like this:
> >
> > int main()
> > {
> > printf("address bus is %d bytes\n",sizeof(void*));
> > }
> > and compile it with cc then run it.
> > If it prints 8, it is a 64 bit OS, if it prints 4, it is a 32 bit OS.
>
> That tells you which architecture the program was compiled for, not
> which architecture the kernel was compiled for. x86_64 can run both
> 32- and 64-bit code.
>
well, if we have a 64-bit kernel /and/ a compiler for 64 bits
architectures, i think that a long int must be 8 bytes, no ?
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-08-20 23:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 18:18 FW: 64 bit or 32 bit Kirkwood, David A.
2007-08-17 21:42 ` terry white
2007-08-19 19:48 ` Benoit Rouits
2007-08-20 18:36 ` Glynn Clements
2007-08-20 23:30 ` Benoit Rouits [this message]
2007-08-21 8:13 ` Glynn Clements
2007-08-20 18:34 ` Glynn Clements
2007-08-21 6:02 ` Carsten Aulbert
2007-08-21 8:27 ` Glynn Clements
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=1187652649.24972.2.camel@localhost \
--to=brouits@free.fr \
--cc=DAVID.A.KIRKWOOD@saic.com \
--cc=glynn@gclements.plus.com \
--cc=linux-admin@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.