On 29/07/2019 18:32, Bruce Dubbs via blfs-dev wrote: > On 7/29/19 11:23 AM, Pierre Labastie via blfs-dev wrote: >> On 29/07/2019 17:59, Bruce Dubbs via blfs-dev wrote: >>> On 7/29/19 5:44 AM, Pierre Labastie via blfs-dev wrote: >>>> On 29/07/2019 11:14, Pierre Labastie via blfs-dev wrote: >>>>> On 29/07/2019 01:58, 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. In this case, I think some 'role="first"' attribute should be >>>>> added >>>>> somewhere. I'll try to figure this out. >>>>> >>>>>> >>>>>> 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) >>>>>> >>>>> >>>>> So I think the role="first" should be added to the dependency on D-Bus on >>>>> the >>>>> Xorg library page. Then elogind should depend on the Xorg libraries, then >>>>> D-Bus should depend on elogind... >>>> >>>> Sorry, looking at the book, I see the order should be: >>>> dbus >>>> elogind >>>> xorg libs >>>> >>>> And looking at the above, I understand that D-Bus should be built first >>>> before >>>> elogind, then again after xorg libs. Is it true? In this case, we should >>>> have: >>>> - xorg-libraries as recommended for D-Bus >>>> - elogind as recommended for xorg libs >>>> - dbus as required with role="first" for elogind >>>> This would generate: >>>> dbus-pass1 >>>> elogind >>>> xorg libs >>>> dbus >>> >>> I just committed an update to address this. Please see if it is sufficient. >>> >> >> Here is the generated order, when ticking: >> X + Window and Display Managers >> ->X Window System Environment >> ->xinit 1.4.1 >> -------------------->8--------- >> python2 >> libuv >> curl >> libarchive >> cmake >> zip >> llvm >> icu >> libxml2 >> sgml-common >> unzip >> DocBook >> docbook-xsl >> libxslt >> pcre >> glib2 >> graphite2-pass1 >> libpng >> which >> freetype2-pass1 >> MarkupSafe >> Mako >> gobject-introspection >> harfbuzz >> freetype2 >> fontconfig >> xorg-env >> util-macros >> xorgproto >> libXau >> xcb-proto >> libXdmcp >> libxcb >> dbus-pass1 >> linux-pam >> elogind >> Xorg libraries >> dbus >> xinit >> pixman >> libdrm >> wayland >> libva >> libvdpau >> wayland-protocols >> mesa >> xbitmaps >> xcb-util >> Xorg Applications >> xcursor-themes >> Xorg fonts >> autoconf213 >> nspr >> js60 >> polkit >> libepoxy >> xorg-server >> xkeyboard-config >> Xorg Legacy >> twm >> xclock >> xterm2 >> libtasn1 >> p11-kit >> make-ca >> ------------>8------------- >> I'm building a system to test that. > > Great. There is one other thing to look at. xorg-server should be built > without --enable-install-setuid. An alternative is to remove the suid bit > from $XORG_PREFIX/libexec/Xorg when testing startx. >
I'll edit the script to remove the switch. It's building the kernel right now. Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
