From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NmqbZ-0003U4-MQ for garchives@archives.gentoo.org; Wed, 03 Mar 2010 15:35:21 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AA88BE090B; Wed, 3 Mar 2010 15:35:09 +0000 (UTC) Received: from mail-ew0-f222.google.com (mail-ew0-f222.google.com [209.85.219.222]) by pigeon.gentoo.org (Postfix) with ESMTP id 6DE04E090B for ; Wed, 3 Mar 2010 15:35:09 +0000 (UTC) Received: by ewy22 with SMTP id 22so1157452ewy.26 for ; Wed, 03 Mar 2010 07:35:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=86h3WWpw4wf9ZD6Ii78vkNFdSkZJfiGnT051/338ees=; b=fGRco7QJYEHOJGbg4uuJslHKJ1j15uR0CVXnMq+hqRKURaAx4D5KG8mbdT8txA8EnS XDHVsPcgD0pkwGIGRR8csT4DAVHPaRzoAjAzWgEfu8X1GQb63fpswdcIdT5KcumNdbzw OYEq1f8XAQcflzCemZcC+QU+ICUKIOvkThUd8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id; b=WdNISU9ThR/mI64kVQo7tHvtU9TkRy23+N2Ni2j/GGghFxtolVxw2lU38pxajaNxV4 OoqXB0TdDezqas75ae+p4Zx58tH3JVVWJMxjj27PKyEdMQMyOM1TLg4PSgt62p7h2qLm iCgQOugbSShMZPVPY14G+LR55E7anc2VNjXeg= Received: by 10.213.67.204 with SMTP id s12mr2218728ebi.76.1267630508814; Wed, 03 Mar 2010 07:35:08 -0800 (PST) Received: from nazgul.localnet (196-210-238-8.dynamic.isadsl.co.za [196.210.238.8]) by mx.google.com with ESMTPS id 7sm15722866eyg.32.2010.03.03.07.35.07 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 03 Mar 2010 07:35:08 -0800 (PST) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Advice for 64-bit n00b? Date: Wed, 3 Mar 2010 17:32:31 +0200 User-Agent: KMail/1.13.0 (Linux/2.6.32-zen6; KDE/4.4.0; x86_64; ; ) References: <008DDC13-5883-4155-A996-64325EFCAA77@stellar.eclipse.co.uk> In-Reply-To: <008DDC13-5883-4155-A996-64325EFCAA77@stellar.eclipse.co.uk> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201003031732.31847.alan.mckinnon@gmail.com> X-Archives-Salt: 317ae9fc-c505-4901-b3d1-243c3a11098c X-Archives-Hash: fcab1ab13fffddcbfb87fc0934c36959 On Wednesday 03 March 2010 17:29:06 Stroller wrote: > Hi there, >=20 > A new (to me) server has 64-bit CPUs. By my standards this is a REALLY > NICE high specification machine (I appears to be 2 x dual-core), but > in fact it's about 3 years old & is one of the earliest Intel Xeons > that supports 64-bits / AMD64 / EMT64. I think it is 64-bit Pentium 4, > rather than Core 2 architecture. >=20 > # cat /proc/cpuinfo | head -n 25 > processor : 0 > vendor_id : GenuineIntel > cpu family : 15 > model : 4 > model name : Intel(R) Xeon(TM) CPU 3.00GHz > stepping : 3 > cpu MHz : 2992.346 > cache size : 2048 KB > physical id : 0 > siblings : 2 > core id : 0 > cpu cores : 1 > apicid : 0 > initial apicid : 0 > fpu : yes > fpu_exception : yes > cpuid level : 5 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge > mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe > syscall nx lm constant_tsc pebs bts pni dtes64 monitor ds_cpl cid cx16 > xtpr > bogomips : 5984.69 > clflush size : 64 > cache_alignment : 128 > address sizes : 36 bits physical, 48 bits virtual > power management: >=20 >=20 > I'm a bit confused by the 36-bit address size mentioned there, but I > assume this is OK. The Gentoo wiki seems to confirm this CPU is 64- > bit: http://tinyurl.com/klv7gc [1] that is correct >=20 > Is there anything I need to know about working with 64-bits / AMD64 / > EMT64, seeing as I've never done so before? Nope, it's just another arch. The days of doing weird funky stuff to get am= d64=20 to work are long gone >=20 > I have started following the Gentoo Linux AMD64 Handbook, because the > Quick Install Guide is described as "x86". Having untarred the stage I > am surprised to find a lib32 directory. I thought compatibility with > 32-bit binaries was optional. Or am I misunderstanding? This is going > to be a headless server & I can't think that it'll need any binary > packages - possibly the management utility for the RAID controller > will be distributed as a binary, I'm not sure yet (the hardware RAID > key was missing when I got this machine =E2=98=B9) >=20 > I'm editing my make.conf and looked at the Gentoo wiki for "Safe > Cflags" - it says 'CHOST=3D"x86_64-pc-linux-gnu"'. But of course > (according to make.conf.example) one shouldn't change CHOST on an > installed system. Will the files in the stage 3 have been compiled > using this CHOST? Yes. If you used a recent amd64 stage, it will all be fine. >=20 > Any pointers would be gratefully appreciated - I'm wondering if > there's anything you guys all take for granted that I could mess up if > I don't allow for it early enough in the installation process. In make,conf, as long s you are using a reasonably recent gcc: CHOST=3D"x86_64-pc-linux-gnu" CFLAGS=3D"-march=3Dnative -O2 -pipe" CXXFLAGS=3D"${CFLAGS}" =2Dmarch=3Dnative avoids all that tedious mucking about with trying to figu= re out=20 what cpu type you should build for, and moves the heavy lifting off onto th= e=20 compiler. =2D-=20 alan dot mckinnon at gmail dot com