Date: Mon, 5 Dec 2005 08:13:50 +0100 From: "Guillaume R." <raimondeau@gmail.com> To: obrien@freebsd.org Cc: freebsd-questions@freebsd.org Subject: Re: A stupid 64bit question ... but ... Message-ID: <7ab0fd580512042313k15a93166i@mail.gmail.com> In-Reply-To: <20051205030253.GC62285@dragon.NUXI.org> References: <20051204184826.D1077@ganymede.hub.org> <20051205030253.GC62285@dragon.NUXI.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2005/12/5, David O'Brien <obrien@freebsd.org>: > > On Sun, Dec 04, 2005 at 06:50:55PM -0400, Marc G. Fournier wrote: > > > > I recently bought a new Intel Xeon server, and when I put it together, = I > > didn't realize that the newer Xeon's were 64bit ... now, I've just buil= t > > perl 5.8.7, and its reporting: > > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > # perl -v > > This is perl, v5.8.7 built for i386-freebsd-64int > .. > > I realize that this may be a stupid question, but am I correct in that > > *this* is a 64bit machine, and I should be enabling the AMD64 stuff on > > her? > > 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). Lo 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" ++
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7ab0fd580512042313k15a93166i>