ALZ (phyglos.org) wrote:
In the book there are several "make -j1" for compiling or "make -j1
check"
for testing clearly marked. However I haven't found any "make -j1
install"
yet. This is what I found unusual in this package.
Why would you ever want to do a parallel install? How much time would
you save? I understand the build and the checks, but the install is the
critical part and the time saved is not significant.
Well, the question is not what I want to do, but what happens in the
context of an LFS/BLFS build by following the instructions.
From the point of view of an LFS builder, I understood (maybe
incorrectly) that I can set MAKEFLAGS to whatever I prefer and go using
the instructions as they are written. When a package has shown problems
with parallel makes, editors clearly advise so in the specific instruction
on the page. This is done with all "make" and "make check" that are know
to need that.
Yes, but we also say: IF a problem occurs "the best way to proceed is to
drop back to a single processor build."
I suppose we could say that we do not recommend MAKEFLAGS or -jN, N>1 for
the install phase.
On your question about why using parallel install, I'd like to do so while
developing/improving my scripts. I've been doing so with LFS and haven't
had trouble until S-Lang.
Generally wouldn't you be installing to a DESTDIR for that? I ran a test
and for slang, the install at -j1 takes about 14 seconds because it wants
to do some extra compilation in the install phase. If you are changing
code, you have most of the files already compiled. My test when I
modified a C file then shows make install to take less than a second at -j1.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
