On Sunday 14 Oct 2012 15:47:31 meino.cra...@gmx.de wrote:
> The compilation of a short C-program from the commandline
> works...the job can be seen in the distcc log on the beaglebone.
>
> But emergeing (in this case "emerge cmus") completly ignores
> distcc
>
> How can I fix it?
Hi,
I've da
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14.10.2012 15:47, meino.cra...@gmx.de wrote:
> Hi,
>
> since my PC /and/ my embedded singlecomputer are involved, I dont
> know whether this is a "normal GENTOO" subject or a "embedded
> GENTOO" one...
>
> What I want: From my embedded system (Bea
Hi,
since my PC /and/ my embedded singlecomputer are involved,
I dont know whether this is a "normal GENTOO" subject or a
"embedded GENTOO" one...
What I want:
>From my embedded system (Beaglebone) I want to sent compilation
jobs to my PC.
I set up cross-compiler on my PC, configured distcc and
On Monday 03 November 2008 22:03:08 Daryl Styrk wrote:
> 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
> >>
> >
-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 di
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy McSpadden wrote:
> On Mon, 2008-11-03 at 14:10 -0500, 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 director
On Mon, 2008-11-03 at 14:10 -0500, Daryl Styrk wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> 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] E
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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: *** [a
On Fri, 12 Oct 2007 19:37:21 -0500
Tim <[EMAIL PROTECTED]> wrote:
> Jerry McBride wrote:
> >
> > I've identified a few packages that simply will not compile when
> > distcc is being used.
> >
> > Has anyone noticed problems with; ncurses, groff or libpcre?
> >
> > I'm thinking about modifying
all my systems running distcc are missing a few links to compilers in
the distcc directories. Seemed to vary across systems.
one was a link to cc (found when compiling ccze for instance) but it was
always one of the less common calls.
The fix was to create a symlink to the generic version.
Chec
Dan Farrell wrote:
> On Fri, 12 Oct 2007 18:26:26 -0400
> Jerry McBride <[EMAIL PROTECTED]> wrote:
>
>>
>> I've identified a few packages that simply will not compile when
>> distcc is being used.
>>
>> Has anyone noticed problems with; ncurses, groff or libpcre?
>>
>> I'm thinking about modifyin
On Fri, 12 Oct 2007 18:26:26 -0400
Jerry McBride <[EMAIL PROTECTED]> wrote:
>
>
> I've identified a few packages that simply will not compile when
> distcc is being used.
>
> Has anyone noticed problems with; ncurses, groff or libpcre?
>
> I'm thinking about modifying /etc/portage/bashrc to d
Jerry McBride wrote:
>
> I've identified a few packages that simply will not compile when distcc
> is being used.
>
> Has anyone noticed problems with; ncurses, groff or libpcre?
>
> I'm thinking about modifying /etc/portage/bashrc to detect a new file
> named /etc/portage/package.distcc that w
I've identified a few packages that simply will not compile when distcc
is being used.
Has anyone noticed problems with; ncurses, groff or libpcre?
I'm thinking about modifying /etc/portage/bashrc to detect a new file
named /etc/portage/package.distcc that will turn off distcc for
each package
15 matches
Mail list logo
