Date: Mon, 5 Dec 2005 04:14:09 -0500 From: Parv <parv@pair.com> To: "Guillaume R." <raimondeau@gmail.com> Cc: freebsd-questions@freebsd.org, obrien@freebsd.org Subject: Re: A stupid 64bit question ... but ... Message-ID: <20051205091409.GB65131@holestein.holy.cow> In-Reply-To: <7ab0fd580512042313k15a93166i@mail.gmail.com> References: <20051204184826.D1077@ganymede.hub.org> <20051205030253.GC62285@dragon.NUXI.org> <7ab0fd580512042313k15a93166i@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
in message <7ab0fd580512042313k15a93166i@mail.gmail.com>, wrote Guillaume R. thusly... > > 2005/12/5, David O'Brien <obrien@freebsd.org>: > > > > On Sun, Dec 04, 2005 at 06:50:55PM -0400, Marc G. Fournier wrote: > > > > > > I didn't realize that the newer Xeon's were 64bit ... now, > > > I've just built perl 5.8.7, and its reporting: > > > > > > # perl -v > > > This is perl, v5.8.7 built for i386-freebsd-64int ... > > Perl won't be reporting a 64-bit capable machine, when running a > > 32-bit OS. Look in /var/run/dmesg for 'AMD Features' to report > > 'LM' (long mode). > > So why there is a 64int? We can suppose that perl has seen that > Marc's proc is a 64 one no? I asked that cause I got a 64bits > (amd) which run on a 32 bits mode and I got oftenly such > "i386-freebsd-64amd" By chance any of you built the Perl w/ USE_64_BIT_INT option? See "perl -V". - Parv --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051205091409.GB65131>