Patrick Machielse wrote:
> Gabriele Greco <gabrielegreco@[EMAIL PROTECTED]
> wrote:
>
>> I'm not using -j feature of makefile, gcc compiles on two threads the
>> two architectures by himself, and I think that forcing this design by
>> default is quite broken also if with enough memory it may be useful.
>
> Have you tried '-j 1'? According to the man page, when you *don't*
> specify a value, make is free to create as many jobs as it sees fit.
>
> My gut feeling is that this is a feature of the build system, not of the
> compiler.
>
> patrick
The OP's problem isn't one of *make* spawning multiple processes, so the
-j option won't help here. Make is simply calling a single instance of
gcc, it's *gcc* that is actually performing a pair of compiles and
lipo-ing them together under the hood.
To the OP:
I suppose you could write a small shell-script that called the two gcc
instances in sequence, followed by the lipo, and use *that* as your
compiler.
--
Clark S. Cox III
clarkcox3@[EMAIL PROTECTED]
|
