From: Daryl Styrk <darylstyrk@gmail.com>
To: Markos Chandras <markos.chandras@gmail.com>
Cc: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] distcc problems
Date: Mon, 03 Nov 2008 15:03:08 -0500 [thread overview]
Message-ID: <490F58FC.9070002@gmail.com> (raw)
In-Reply-To: <200811032141.14419.markos.chandras@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Markos Chandras wrote:
> On Monday 03 November 2008 21:10:37 Daryl Styrk wrote:
>> I thought I had everything set up correctly but apparently not.
>>
>> distccd[6820] (doc_execvp) ERROR: failed to exec x86_64-pc-linux-gnu-gcc
>>
>> : No such file or directory
>>
>> distccd[1246] ERROR: compile args.c on 10.0.1.8 failed with exit code 110
>> make: *** [args.o] Error 110
>> *
>> * ERROR: dev-util/ctags-5.7 failed.
>> * Call stack:
>> * ebuild.sh, line 49: Called src_compile
>> * environment, line 2107: Called die
>> *The specific snippet of code:
>> * emake || die "emake failed"
>> * The die message:
>> * emake failed
>>
>> I'm pretty new to gentoo, and linux this far 'in' any help would be
>> greatly appreciated. I just finished the base install and figured this
>> would be nice to help speed along compiling the rest of the system.
>>
>> I'm a little lost where to start and where I might have gone wrong.
>>
>> Any pointers to steer me back in the right direction?
>
> Are we talking about cross-compile too? What are the arches of your gentoo
> boxes?Tell us more about your configuration. Arches, who is compiling the
> packages for whom etc. :)
>
Sorry,
I would like to compile packages for gentoo.
Gentoo
uname -a
2.6.25-gentoo-r7 #1 SMP x86_64 Intel Core 2 Duo CPU T7500 @ 2.20GHz
gcc -v 4.1.2
Ubuntu 8.04
uname -a
2.6.25-21-generic #1 SMP x86_64 Intel Core 2 Duo CPU T550 @ 1.83GHz
gcc -v 4.2.4 (ubuntu 4.2.4-1ubuntu3)
some further reading looks like not having matching gcc versions will be
problematic and makes sense.
Could that be the exit code 110?
Any other system information needed?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJD1j8ejxzjThnMmIRAuLBAJwK7u1XDKPuHpd8DqarlIItkCJvLQCeJFK9
qlysWBrdD7pcZpw49DOQy9Q=
=1VAk
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-11-03 20:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 19:10 [gentoo-user] distcc problems Daryl Styrk
2008-11-03 19:13 ` Jeremy McSpadden
2008-11-03 19:18 ` Daryl Styrk
2008-11-03 19:41 ` Markos Chandras
2008-11-03 20:03 ` Daryl Styrk [this message]
2008-11-03 20:46 ` Markos Chandras
-- strict thread matches above, loose matches on Subject: below --
2007-10-12 22:26 [gentoo-user] Distcc problems Jerry McBride
2007-10-12 22:33 ` Dan Farrell
2007-10-13 4:32 ` Tim
2007-10-13 13:57 ` William Kenworthy
2007-10-13 0:37 ` Tim
2007-10-13 14:56 ` Jerry McBride
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=490F58FC.9070002@gmail.com \
--to=darylstyrk@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=markos.chandras@gmail.com \
/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