The gcc-ar.o, gcc-nm.o, gcc-ranlib.o and errors.o included
config.h which was a generated file. But no explicity rule
to clarify the dependency. There was potential building
failure while parallel make.
For gcc-ar.o, gcc-nm.o and gcc-ranlib.o, they were compiled from one C
source file gcc-ar.c, we
On 07/25/2014 11:48 PM, Saul Wold wrote:
Can you please rebase this against master as we have already merged
the first version.
No problem, I am working on it
//Hongxu
Thanks
Sau!
On 07/25/2014 03:13 AM, Hongxu Jia wrote:
The gcc-ar.o, gcc-nm.o, gcc-ranlib.o and errors.o included
Can you please rebase this against master as we have already merged the
first version.
Thanks
Sau!
On 07/25/2014 03:13 AM, Hongxu Jia wrote:
The gcc-ar.o, gcc-nm.o, gcc-ranlib.o and errors.o included
config.h which was a generated file. But no explicity rule
to clarify the dependen
The gcc-ar.o, gcc-nm.o, gcc-ranlib.o and errors.o included
config.h which was a generated file. But no explicity rule
to clarify the dependency. There was potential building
failure while parallel make.
For gcc-ar.o, gcc-nm.o and gcc-ranlib.o, they were compiled from one C
source file gcc-ar.c, we
On Wed, Jul 23, 2014 at 6:48 PM, Hongxu Jia wrote:
> In subdir 'gcc', Most C source files included config.h which was
> generated by a rule. But no related prerequisites was added to
> the C source compiling rule. There was potential building failure
> while makefile enabled parallel.
>
> The C so
In subdir 'gcc', Most C source files included config.h which was
generated by a rule. But no related prerequisites was added to
the C source compiling rule. There was potential building failure
while makefile enabled parallel.
The C source compiling rule used suffix rule '.c.o', but the suffix
rul
