From: Fernando Rodriguez <frodriguez.developer@outlook.com>
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 [thread overview]
Message-ID: <BLU436-SMTP369AF3BCA2B22423CEE7EA8DD20@phx.gbl> (raw)
In-Reply-To: <20150504194154.GA23730@waltdnes.org>
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
next prev parent reply other threads:[~2015-05-04 20:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 1:10 [gentoo-user] Difference between "normal distcc" and "distcc with pump"? Walter Dnes
2015-05-03 18:57 ` Fernando Rodriguez
2015-05-04 3:59 ` Walter Dnes
2015-05-04 9:29 ` Fernando Rodriguez
2015-05-04 9:38 ` Fernando Rodriguez
2015-05-04 15:40 ` Walter Dnes
2015-05-04 19:41 ` Walter Dnes
2015-05-04 20:36 ` Fernando Rodriguez [this message]
2015-05-04 22:06 ` Fernando Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BLU436-SMTP369AF3BCA2B22423CEE7EA8DD20@phx.gbl \
--to=frodriguez.developer@outlook.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox