On Sun, Jul 28, 2019 at 06:58:14PM -0500, Bruce Dubbs via blfs-dev wrote:
> On 7/28/19 5:40 PM, Ken Moffat via blfs-dev wrote:
> >
> > So, jhalfs thingk dbus only needs to be built once ?
> >
> > The book recommends building it twice :
> >
> > D-Bus Dependencies
> > Recommended
> >
> > Xorg Libraries (for dbus-launch program) elogind-241.3 (first build
> > without, and then again after elogind is installed)
>
> Looks like jhalfs only identifies one build. Automating circular
> dependencies correctly is a tough job.
>
Agreed.
> To me the above wording is a little ambiguous. I think the following might
> be better:
>
> Xorg Libraries and elogind-241.3 (first build
> before these packages, and then again after both are installed)
>
I didn't initially see the ambiguity, but your wording does improve
it.
However, going back to Roger's post which started this (and I'm
assuming he's using the sysv book), I wonder if elogind had not been
started by the bootscript ?
Also - I've now done a bit of reading about elogind, and according
to gentoo it needs Control Group support (CONFIG_CGROUPS) and
Inotify support (presumably CONFIG_INOTIFY_USER). For the systemd
book those are mentioned, along with many other things, in LFS
s8.3.1 but not in the sysv LFS book.
Since elogind is not required for most non-Xorg builds, I suppose
that kernel config information should be added to elogind ?
ĸen
--
One pill makes you larger, And one pill makes you small.
And the ones that mother gives you, Don't do anything at all.
Go ask Alice, When she's ten feet tall.
-- Jefferson Airplane, White Rabbit
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
