Hi,
Pierre, and probably some other people here, will know that I use my
own buildscripts, and in many cases I drop recommended dependencies
(with added switches where needed), or add optional dependencies
(ditto), as well as other variations such as NOT building in
/sources (for me, that is an nfs mount, I want to build on a local
disk).
It occurs to me that I can probably get another machine (ryzen
based, separate question about nouveau on -chat) with plentiful
processors and memory to mostly use for getting a step nearer
towards continuous integration (i.e. as a first step build LFS for
the machine, then try variations of desktop sysv systems to see what
breaks). Whether I can diagnose the breakages is somewhat less
likely, these days I'm usually late enough in testing a fresh build
that often someone has already found the problem.
However, the online documentation appears to be somewhat outdated
(that is perfectly normal in linux, of course), so I'll start by
asking three questions:
1. Can jhalfs reliably build desktop BLFS in chroot (things like
JS78 and firefox) ? I used to almost-always build on the freshly
booted system unless I was expecting problems, but nowadays I find
it far more convenient to build most, or all, of my normal desktop
in chroot because the build is so slow and if things break I'm naked
without my browsers ;-) In the book we have notes on environment
(SHELL=/bin/sh etc) but has anybody tried this or is it actually
broken in jhalfs ?
2. Does jhalfs easily support -jN builds ? I could not see that
mentioned in the svn docs, apologies if I've missed it. My plan
would probably be to build a base LFS system (initially using my own
scripts to tune it for the box in terms of things like firmware and
kernel config), image that, then use it to build "minimal" Xorg
(minimal in jhalfs terms, probably builds a lot of things that I
currently ignore at that stage). Then image that and build
different desktop environments.
Using -jN and only building one system at a time is important
because of things like rust. I've spent a few days trying to use
libcgroup on sysv (rust apparently accepts cpu restrictions from
that) but given up in disgust (it's too hard to configure). So
anytime I build rust it thinks it can use N+2 cores of my machine.
That also means that a big machine will need a lot of memory.
Of course, an alternative use for a build machine is to allocate N
systems and build something on each of them using -j1 (just to test
if it builds). Because of rust (and ninja in qtwebengine) I don't
think I'll ever do that.
3. I recall that DejaVu is recommended as a runtime dependency for
some things. I'm sort-of thinking about building desktops and then
seeing if they seem to work - I suppose I'd have to provide my own
extra scripts to install dejavu ? If so, I might cheat and just
copy the TTFs from local storage into /usr/share/fonts.
At this point I have doubts about all of this, even about what will
be a useful spec for the machine (even how much local storage will
be useful, so I don't think this is going to happen very quickly.
TIA
ĸen
--
Internal error in fortune program:
fnum=2987 n=45 flag=1 goose_level=-232323
Please write down these values and notify fortune program admin.
--
http://lists.linuxfromscratch.org/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
