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 6CFEB138CCC for ; Mon, 4 May 2015 20:38:14 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7958BE08F6; Mon, 4 May 2015 20:38:07 +0000 (UTC) Received: from BLU004-OMC1S38.hotmail.com (blu004-omc1s38.hotmail.com [65.55.116.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 50035E08ED for ; Mon, 4 May 2015 20:38:06 +0000 (UTC) Received: from BLU436-SMTP36 ([65.55.116.9]) by BLU004-OMC1S38.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Mon, 4 May 2015 13:38:06 -0700 X-TMN: [6xa2igJxFgyVthswiBmyHwdECDxAQm9pfglwUrxgSOg=] X-Originating-Email: [frodriguez.developer@outlook.com] Message-ID: From: Fernando Rodriguez To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Difference between "normal distcc" and "distcc with pump"? Date: Mon, 4 May 2015 16:36:08 -0400 User-Agent: KMail/4.14.3 (Linux/4.0.1; KDE/4.14.3; x86_64; ; ) In-Reply-To: <20150504194154.GA23730@waltdnes.org> References: <20150503011001.GA30510@waltdnes.org> <20150504194154.GA23730@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-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-OriginalArrivalTime: 04 May 2015 20:38:05.0350 (UTC) FILETIME=[390D9C60:01D086AA] X-Archives-Salt: 15f5c993-6cc5-40b1-8109-7bd79a28227f X-Archives-Hash: 3bb7ad1f4fd273a85a9e44728e87d7d7 On Monday, May 04, 2015 3:41:54 PM Walter Dnes wrote: > Why is seamonkey the only program (so far for me) that needs "-m32"? > Would it need "-m64" if it was being cross-compiled on a 32-bit host > system for 64-bit client? Is there a wiki that we can contribute this > info to? It has to do with my last post. Basicly the makefiles are invoking the full compiler name for the files that are meant to run on the target but it invokes just gcc for the files that are meant to run on the host. This is in the context of cross-compiling, not distcc, so the file that's failing is meant to run locally (it's a custom build tool). If you where compiling locally (or in two machines with the same compiler) it would not matter cause the host and target compiler are the same, but when distcc comes in it builds those files with the host (system) compiler on the host. Changing the c++, cc, gcc, and g++ symlinks to a wrapper script that invokes the compiler by it's full name as show in the RaspberryPi wiki page *should* fix it. -- Fernando Rodriguez