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.62) (envelope-from ) id 1H33rE-00034x-CI for garchives@archives.gentoo.org; Sat, 06 Jan 2007 05:12:40 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id l065Ap1r021252; Sat, 6 Jan 2007 05:10:51 GMT Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by robin.gentoo.org (8.13.8/8.13.8) with ESMTP id l065Ap4N019995 for ; Sat, 6 Jan 2007 05:10:51 GMT Received: from list by ciao.gmane.org with local (Exim 4.43) id 1H33pL-0006AU-Md for gentoo-amd64@lists.gentoo.org; Sat, 06 Jan 2007 06:10:43 +0100 Received: from ip68-231-13-122.ph.ph.cox.net ([68.231.13.122]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 06 Jan 2007 06:10:43 +0100 Received: from 1i5t5.duncan by ip68-231-13-122.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 06 Jan 2007 06:10:43 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: qt3 Date: Sat, 6 Jan 2007 05:10:37 +0000 (UTC) Message-ID: References: <200701060330.11384.sheridan@stavcom.ru> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-13-122.ph.ph.cox.net User-Agent: pan 0.120 (Plate of Shrimp) Sender: news X-Archives-Salt: 45fa00cd-7397-4d0a-8268-8f8934ab7f5e X-Archives-Hash: 8952595723abc0bdd5a23d6306a0184b "=?utf-8?b?0JPQvtGA0LvQvtCy?= =?utf-8?b?INCcLtCSLg==?=" posted 200701060330.11384.sheridan@stavcom.ru, excerpted below, on Sat, 06 Jan 2007 03:30:11 +0300: > Why qt3 build with linux-g++ , hot with linux-g++-64? I'm not the Qt maintainer, so this is simply a guess, but without investigating to deeply, probably because portage isn't setup to handle full dual-arch, that is, with a few toolchain exceptions (glibc, gcc, binutils, portage's sandbox) it handles 64-bit only, on amd64. If you want 32-bit, you either emerge the precompiled 32-bit binaries, or use a 32-bit chroot, thus keeping the 32-bit portage database separate from the main system (64-bit) portage database. Since portage doesn't have to worry about keeping the two separate, the Qt build can use the generic linux-g++, instead of having to track 64-bit separately from 32-bit as it would if they were built and delivered together in the same package. -- 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 -- gentoo-amd64@gentoo.org mailing list