[distcc] solaris execvp/e2big problem
Corrado Giacomini
Corrado.Giacomini at trema.com
Fri Oct 25 11:59:01 GMT 2002
Well,
I find out htat the problem was my compilation script.
As suggested in distcc documentation I have created a shell script on
both the volunteer machine where I run distccd and the local machine
where I invoke distcc.
The script was missing the interpreter as first line, so I add it and it
now it work fine..
#!/bin/bash
/usr/gnu/gcc31/bin/gcc -b sparc-sun-solaris2.7 -V 3.1.1 $*
-Corrado
Martin Pool wrote:
>On 25 Oct 2002, Corrado Giacomini <Corrado.Giacomini at trema.com> wrote:
>
>
>
>>I arranged to figure out how big is the argument list I am passing
>>to the execvp system call and I have found that is 4834 bytes in
>>size.
>>
>>
>
>Wow, that's a very low limit.
>
>
>
>>My question are:
>>
>>How I can figure out which of the above limits are effectively set on my
>>system ?
>>
>>
>
>I don't know. Ask Sun?
>
>
>
>>would be feasible to rewrite the function mentioned above in order
>>to use, just for example the system call system() ?
>>
>>
>
>system() is not a system call, it's a function that ends up calling
>execv(). I can't see how using system() would make things any better.
>
>Presumably there is some Solaris-specific thing you have to do to make
>it accept all the arguments.
>
>distcc doesn't do anything special to linker invocations, it just runs
>them locally. If it works with plain cc it ought to work with
>distcc.
>
>You could try running truss on Make to see how it exec()s the linker.
>
>
>
-------------- next part --------------
HTML attachment scrubbed and removed
More information about the distcc
mailing list