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 E3B92138CAE for ; Mon, 4 May 2015 03:59:46 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 81455E0884; Mon, 4 May 2015 03:59:39 +0000 (UTC) Received: from ironport2-out.teksavvy.com (ironport2-out.teksavvy.com [206.248.154.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 61AB7E0824 for ; Mon, 4 May 2015 03:59:38 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AucGAGvvdVRo9+pE/2dsb2JhbAA3gVOeU4McgQiBdQEBBAE6HCgLCxIPExIPBSUQJ4gAohGMIRQQCAICAh0Dgz4DPBaCO2MEjVWHYYVtjRg X-IPAS-Result: AucGAGvvdVRo9+pE/2dsb2JhbAA3gVOeU4McgQiBdQEBBAE6HCgLCxIPExIPBSUQJ4gAohGMIRQQCAICAh0Dgz4DPBaCO2MEjVWHYYVtjRg X-IronPort-AV: E=Sophos;i="5.11,557,1422939600"; d="scan'208";a="118167698" Received: from 104-247-234-68.cpe.teksavvy.com (HELO waltdnes.org) ([104.247.234.68]) by ironport2-out.teksavvy.com with SMTP; 03 May 2015 23:59:36 -0400 Received: by waltdnes.org (sSMTP sendmail emulation); Sun, 03 May 2015 23:59:08 -0400 From: "Walter Dnes" Date: Sun, 3 May 2015 23:59:08 -0400 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Difference between "normal distcc" and "distcc with pump"? Message-ID: <20150504035908.GA1014@waltdnes.org> References: <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 In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Archives-Salt: 705f9c86-4f04-4b9c-b1fd-87dcfb1244af X-Archives-Hash: e1ae09bd6e3232d250368bd4020960c9 On Sun, May 03, 2015 at 02:57:46PM -0400, Fernando Rodriguez wrote > Some packages do custom preprocessing and other weird things during > the build process that cause problems with pump mode since it caches > copies of the unmodified headers. If you're lucky it just fails (and > usually falls back on compiling locally), if you're not then it may > succeed and you'll get runtime bugs. I haven't find a package yet > that fails without pump mode as long as your CFLAGS are set properly. Seamonkey fails during the build process. Two tries, and the build log was 74,046 bytes each time. I have an Intel x86_64 as the host, and an Atom i686 (32-bit only) as the client. Given your description, I may drop "pump" altogether from my "xmerge" script. I'll unmerge seamonkey-bin, and try distcc-building seamonkey from source, without "pump", Monday when I have more time. Here are a few lines from the failed build log, using "pump"... Executing: gcc -o nsinstall_real -march=atom -mtune=atom -fstack-protector -pipe -mno-avx -DXP_UNIX -MD -MP -MF .deps/nsinstall_real.pp -O2 -DUNICODE -D_UNICODE -Wl,-O1 -Wl,--as-needed host_nsinstall.o host_pathsub.o /usr/lib/gcc/i686-pc-linux-gnu/4.8.4/../../../../i686-pc-linux-gnu/bin/ld: i386:x86-64 architecture of input file `host_nsinstall.o' is incompatible with i386 output /usr/lib/gcc/i686-pc-linux-gnu/4.8.4/../../../../i686-pc-linux-gnu/bin/ld: i386:x86-64 architecture of input file `host_pathsub.o' is incompatible with i386 output /usr/lib/gcc/i686-pc-linux-gnu/4.8.4/../../../../i686-pc-linux-gnu/bin/ld: host_nsinstall.o: file class ELFCLASS64 incompatible with ELFCLASS32 /usr/lib/gcc/i686-pc-linux-gnu/4.8.4/../../../../i686-pc-linux-gnu/bin/ld: final link failed: File in wrong format -- Walter Dnes I don't run "desktop environments"; I run useful applications