From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1EA7td-00036Q-Te for garchives@archives.gentoo.org; Tue, 30 Aug 2005 15:19:34 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j7UFH3OD032405; Tue, 30 Aug 2005 15:17:03 GMT Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j7UFH1ev012814 for ; Tue, 30 Aug 2005 15:17:02 GMT Received: from steiner.cc.vt.edu (IDENT:mirapoint@evil-steiner.cc.vt.edu [10.1.1.14]) by lennier.cc.vt.edu (8.12.11/8.12.11) with ESMTP id j7UFJ9OA020609 for ; Tue, 30 Aug 2005 11:19:09 -0400 Received: from [128.173.184.73] (gs4073.geos.vt.edu [128.173.184.73]) by steiner.cc.vt.edu (MOS 3.6.4-CR) with ESMTP id DUM17308; Tue, 30 Aug 2005 11:19:06 -0400 (EDT) Message-ID: <431478DB.6090404@gentoo.org> Date: Tue, 30 Aug 2005 11:18:51 -0400 From: "Stephen P. Becker" User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050807) X-Accept-Language: en-us, en Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-mips@gentoo.org Reply-to: gentoo-mips@lists.gentoo.org MIME-Version: 1.0 To: gentoo-mips@lists.gentoo.org Subject: [gentoo-mips] profiles References: <42F7492B.5080306@gentoo.org> <20050811200505.GH30724@puck.ch> <42FBCF8C.7090103@gentoo.org> <20050812064720.GI30724@puck.ch> <42FC96AB.6010200@gentoo.org> <20050813101402.GL30724@puck.ch> In-Reply-To: <20050813101402.GL30724@puck.ch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 0c877a7b-852f-4dd7-b130-49e9d6463660 X-Archives-Hash: 87d8de740f48abba166676cc4a04358b Hi folks, With the somewhat recent introduction of support for a wide variety of SGI machines under gentoo, expanding to include all of Indy/Indigo2, Origin, Octane, Indigo2 Impact (ip28), and O2, I've noticed more than just a handful of new users have had problems when getting to the kernel compile phase of the install. The problem is that on systems that only run 64-bit kernels, you need a mips64-unknown-linux-gnu toolchain to build the kernel. Since the userland is all 32-bit, the native toolchain isn't good enough to compile the kernel. However, we do provide a proper toolchain via the gcc-mips64 ebuild. Furthermore, binutils supports mips64 by default, but symlinks must exist such that we have mips64-unknown-linux-gnu-ld -> ld, etc. Both of these are automatically provided during emerge system if you use the correct profile, which is default-linux/mips/mips64/2005.0 currently. The problem is that all of our stages ship with default-linux/mips/2005.0 as the default profile, which does *not* provide gcc-mips64 and the binutils symlinks. Therefore if a user didn't know any better and didn't change their profile appropriately, they would be stuck while trying to build their kernel because the native 32-bit toolchain in the userland will just spit out errors and die when compiling the kernel. Of course, this is easily fixed by emerging gcc-mips64 and running "binutils-config --mips", which will set up a proper toolchain. However, by that time, the user is discouraged a bit and inevitably finds our irc channel and whines that Gentoo is broken. Now, I have a few ideas for getting around this. Obviously whatever is decided should be added to the documentation, but here are some ideas: A) Do nothing...document in the handbook that if your machine is 64-bit, you *must* select the mips64 sub-profile. (I don't like this because some folks may be confused as to why everything still works just fine with the mips profile, and/or they will just skim over that and keep going) B) Similar to A, except ship stages without the profile set. That way, folks really are stuck until they set the proper profile. (I don't like this because they could still be confused and set the mips profile) C) Make default-linux/mips/ provide all the 64-bit stuff and get rid of the mips64 sub-profile, since all of the SGI machines we support can run 64-bit kernels if you so choose (ip22 is the only system that supports a 32-bit kernel at this time). D) (Kumba's idea here...) Have machine specific profiles, e.g. default-linux/mips/ip22, default-linux/mips/ip32, etc. (This could be really useful because it would allow us to do some other machine specific voodoo in the profile). Any thoughts? -Steve -- gentoo-mips@gentoo.org mailing list