It seems that environment vars set by mozilla build confuse lto-wrapper with:
lto-wrapper: error trying to exec 'make -j1': execvp: No such file or directory
cut&pasting the compilation command line and executing it by hand works well.
Does it set MAKE? I suppose we need to split (and preserve?) arguments :/
grep didn't seem to find any interesting positives on this. However I did not update my mozilla tree since last build that did not reproduce this and nothing seems to have changed on GCC side. I think evans got updated, so perhaps it is feature of new GNU Make to prevent fork bombs?
Mozilla Makefiles do not use "+" clauses and I simply use hard wired -flto=24 setting.
Has this been fixed?
No response and unclear bug.
> No response and unclear bug.
It is still there. In lto-wrapper.c we do
new_argv = getenv ("MAKE");
and when MAKE is set to something like "make -j" we try to execute it...
Ok, you didn't state that Mozilla indeed sets MAKE to 'make -j'. Yes, if that
happens there is a problem.
2010-05-23 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
* lto-wrapper.c (run_gcc): Unset MAKEFLAGS and MFLAGS
before calling make; allow override through $MAKE.
* doc/invoke.texi (Optimize Options): Document override.
simply checking with access (..., X_OK) of course doesn't work (that doesn't
search the path...).
This no longer happens with recent Firefox builds, but I think it was rather fixed at Firefox buildsystem...
(In reply to Jan Hubicka from comment #8)
> This no longer happens with recent Firefox builds, but I think it was rather
> fixed at Firefox buildsystem...
That sounds like WORKSFORME then.