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 1PlmTm-00061R-Qw for garchives@archives.gentoo.org; Sat, 05 Feb 2011 18:03:27 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 51D571C0A5 for ; Sat, 5 Feb 2011 18:03:26 +0000 (UTC) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by pigeon.gentoo.org (Postfix) with ESMTP id 85B861C074 for ; Sat, 5 Feb 2011 17:52:33 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PlmJE-0006vL-6h for gentoo-amd64@lists.gentoo.org; Sat, 05 Feb 2011 18:52:32 +0100 Received: from ip68-231-22-224.ph.ph.cox.net ([68.231.22.224]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 05 Feb 2011 18:52:32 +0100 Received: from 1i5t5.duncan by ip68-231-22-224.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 05 Feb 2011 18:52:32 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: New install - basic question Date: Sat, 5 Feb 2011 17:52:21 +0000 (UTC) Message-ID: References: <201102051545.08854.gentoo@appjaws.plus.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-22-224.ph.ph.cox.net User-Agent: Pan/0.133 (House of Butterflies; GIT 25ed40d branch-testing) Content-Transfer-Encoding: quoted-printable X-Archives-Salt: X-Archives-Hash: 9142fa6206766c1befafb9250f21597d Paul Stear posted on Sat, 05 Feb 2011 15:45:08 +0000 as excerpted: > I am currently using amd64 2 core processor but now have the chance > to use an intel quad 64 processor. > This might be a silly question but is it best to do a compltly new > install? If so which stage do I download from the following list:- > =20 > alpha: iso stages=20 > amd64: iso stages=20 > arm: stages=20 > hppa: stages=20 > ia64: iso stages=20 > ppc/ppc64: iso stages=20 > s390/s390x: stages=20 > sh: stages=20 > sparc: iso stages=20 > x86: iso stages >=20 > Which chost and cflags should I use? Intel em64t (as opposed to the Itanics/Itaniums) is amd64 by another name= . So use the amd64 stages if you want 64-bit, or the x86 stages if you want legacy 32-bit. (FWIW, ia64, Intel Arch 64, would be for the Itaniums. =20 Sometimes people get that mixed up, but unless you know you have that=20 hardware, it's pretty safe to assume it's amd64/em64t/x86_64, NOT ia64.) Assuming amd64, whether you /have/ to start from fresh stages or can use=20 your existing install, depends on how similar the hardware extensions are= ,=20 and whether you used -march or -mtune on your previous install. If you=20 used -mtune, the old install should work as it will have used only=20 instruction ordering for your target hardware, with generic instructions. If you used -march, it will have used targeted instructions as well, and=20 may or may not work. You can try it if you like as going older to newer=20 it's likely to work, but really, starting with a new CPU is a good excuse= =20 to start fresh, eliminating any possible cruft left over from the old=20 system, so I'd recommend starting from new stages even if the old ones=20 would work, unless you're lazy and simply want to avoid that extra=20 compiling. If you want to target the new hardware and are using a new enough gcc (I=20 think the stage supplied one is new enough, now), you can simply use=20 -march=3Dnative to take advantage of its instructions. If you'd prefer t= o=20 have the compiled packages be installable on either machine (say if you=20 run FEATURES=3Dbuildpkg to get the binpkgs to do so), but tuned for the n= ew=20 one, use -mtune=3Dnative on the new one instead, possibly with -march set= =20 for the common subset of both instruction sets, tho you'd of course have=20 to set that subset specifically, which means researching what it is. CHOST will normally be the same, x86_64-pc-linux-gnu , unless you're doin= g=20 something strange or using legacy 32-bit x86 instead of amd64. --=20 Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman