From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Difference between "normal distcc" and "distcc with pump"?
Date: Sun, 3 May 2015 23:59:08 -0400 [thread overview]
Message-ID: <20150504035908.GA1014@waltdnes.org> (raw)
In-Reply-To: <BLU436-SMTP160514BB0A7E63385C39BE28DD30@phx.gbl>
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 <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
next prev parent reply other threads:[~2015-05-04 3:59 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 [this message]
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
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=20150504035908.GA1014@waltdnes.org \
--to=waltdnes@waltdnes.org \
--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