On Sat, 2020-09-19 at 12:41 -0500, Douglas R. Reno via blfs-dev wrote: > On 9/19/20 7:46 AM, Wayne Blaszczyk via blfs-dev wrote: > > Hi All, > > > > Not sure if anyone else has noticed this, but with the right conditions, > > glib-2.66.0 will install gtk-doc-1.32.1. > > On a fresh build box I had gtk-doc-1.32 installed, and was in the process > > of building glib-2.66.0 (for the second time) when it failed with a git not > > found error. > > On closer inspection, it was trying to git clone gtk-doc repo due to not > > meeting the gtk-doc >= 1.32.1 requirement as a fallback. > > After installing git, this time the glib-2.66.0 build was successfully and > > on closer inspection, it had actually installed the gtk-doc-1.32.1 > > subproject. > > what make it worse is that there is no gtk-doc 1.32.1 release, but in fact > > just the latest from git repo from what I can tell. > > This is not the first time I had noticed a "fallback" with a meson gnome > > package build recently. I'm not happy that dependencies are being installed > > without consent. > > > > Regards, > > Wayne. > > > > > Hi Wayne, > > > Are you building glib with -Dgtk_doc=true by chance? A couple of us have > tried building glib2 with gtk-doc installed, and without gtk-doc > installed, and we're unable to reproduce this problem. We have known it > to happen from time to time, but we'd like to know exactly what causes > it as well.
Yes, I'm using -Dgtk_doc=true . I've attached the output of the build. See line 348-352 and around 4134. One way to detect if this scenario has occurred or not is to check the version of /usr/share/pkgconfig/gtk-doc.pc after the build/install. Version: 1.32.1 would indicate that it had. Wayne. > > I'm not happy about dependencies being installed without consent either. > > - Doug >
shell.log.xz
Description: application/xz
-- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
