From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id D10E9138CAE for ; Sun, 3 May 2015 01:10:37 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D2C25E08EF; Sun, 3 May 2015 01:10:30 +0000 (UTC) Received: from ironport2-out.teksavvy.com (ironport2-out.teksavvy.com [206.248.154.181]) by pigeon.gentoo.org (Postfix) with ESMTP id D5D8AE08E2 for ; Sun, 3 May 2015 01:10:29 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgUFAGvvdVRsr+w6/2dsb2JhbAA3gVOhb4EIgX0CNxxfEyEFFBEkE4gJjBOVdYt/ChgFBQoQCAICAh0Dgz4DOQMHgkpjBI1VhTqCJ4VtiECEWA X-IPAS-Result: AgUFAGvvdVRsr+w6/2dsb2JhbAA3gVOhb4EIgX0CNxxfEyEFFBEkE4gJjBOVdYt/ChgFBQoQCAICAh0Dgz4DOQMHgkpjBI1VhTqCJ4VtiECEWA X-IronPort-AV: E=Sophos;i="5.11,557,1422939600"; d="scan'208";a="118107542" Received: from 108-175-236-58.dsl.teksavvy.com (HELO waltdnes.org) ([108.175.236.58]) by ironport2-out.teksavvy.com with SMTP; 02 May 2015 21:10:27 -0400 Received: by waltdnes.org (sSMTP sendmail emulation); Sat, 02 May 2015 21:10:01 -0400 From: "Walter Dnes" Date: Sat, 2 May 2015 21:10:01 -0400 To: Gentoo Users List Subject: [gentoo-user] Difference between "normal distcc" and "distcc with pump"? Message-ID: <20150503011001.GA30510@waltdnes.org> 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=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-Archives-Salt: e0e1b8a3-1ec5-41dd-905b-d8f7606f696c X-Archives-Hash: 11d2d39c7f1b326369bbc1a897914c61 I ran into a couple of problems with distcc cross-compiling on a 64-bit host for a 32-bit host. One was with ffmpeg, and the other one was seamonkey (built-from-source). There's a thread at http://www.gossamer-threads.com/lists/gentoo/user/298324 which mentions ffmpeg with symptoms identical to mine. ffmpeg is no problem doing locally. But seamonkey built-from-source is a 14 hour marathon on the ancient 32-bit Atom. It's the reason I got into distcc in the first place. Fortunately, seamonkey-bin exists, and builds properly. Basic Youtube videos (End Of The Line; Travelling Wilburys; HTML5; H264; 360-line-resolution) peg the double-core Atom with a cpu load of 2.75. That's not Seamonkey's fault; what do you expect from an Atom, driving an un-accelerated framebuffer? I'm happy that the devs went to the trouble of reverse-engineering the Poulsbo (bleagh) chip. The thread listed above mentions that distcc without "pump" can sometimes solve crossdev build problems. Can it be used to build seamonkey from source on the host and manually push it to the client? While we're on the topic of distcc, it's update time. The client shows... aa1 ~ # gcc-config -l [1] i686-pc-linux-gnu-4.8.4 * ...and the host shows... [d531][waltdnes][~] gcc-config -l [1] i686-pc-linux-gnu-4.8.3 * [2] x86_64-pc-linux-gnu-4.8.4 * According to the crossdev "--help" listing... -S, --stable Use latest stable versions as default -C, --clean target Uninstall specified target This implies that on the host, I should do the following... crossdev -C -t i686-pc-linux-gnu crossdev -S -t i686-pc-linux-gnu Before I take the plunge, can anybody with experience confirm that this is the correct way to do it? -- Walter Dnes I don't run "desktop environments"; I run useful applications