Using polkit-0.118 and our
polkit-0.118-fix_elogind_detection-1.patch, autoreconf fails with
current versions of everything. In my script I use autoreconf -fiv
instead of just autoreconf -fi, so this maybe shows a little more
detail than the book's version:
(the first part looks ok)
autoreconf: running: intltoolize --copy --force
autoreconf: running: gtkdocize --copy
Can't exec "gtkdocize": No such file or directory at
/usr/share/autoconf/Autom4te/FileUtils.pm line 293.
autoreconf: error: gtkdocize failed with exit status: 2
The only relevant stuff I can find is old (2018) bug reports from
debian (e.g. 89911) -
| Recent versions of dh-autoreconf automatically run gtkdocize if gtk-doc
| is found in configure.ac. This caused gstreamer1.0/1.14.1-1 to FTBFS on
| all architectures (except amd64 and all which were built by the uploader,
| presumably on a non-minimal system).
And from one of the posts on debian 89891 - (dh-autoreconf) -
| Version 18 invokes gtkdocize without a way to disable this, although
| it does not depend on gtk-doc-tools.
|
| This breaks e.g. building libtasn1-6 which has gtk-doc-tools only in
| Build-Depends-Indep because it uses --disable-gtk-doc on binary-only
| builds.
|
| Please either add a dependency or(and) add a way to disable running
| gtkdocize.
From that, I guess that the change to autoconf-2.70 has buggered
this. From the release notes for 2..70 (pasted from lwn.net) :
*** autoreconf will now run gtkdocize and intltoolize when appropriate.
From the release notes of autoconf-2.70-2.mga8 at mageia cauldron -
* Sun Jul 26 2020 daviddavid <daviddavid> 1:2.69.221-d0ac.5.mga8
+ Revision: 1609074
- add missing dependency on gtk-doc
* autoreconf: running: gtkdocize --copy
Can't exec "gtkdocize": No such file or directory at
/usr/share/autoconf/Autom4te/FileUtils.pm line 292, <GEN3> line 6
Which sounds a painfully heavy remedy. As a quick attempt I tried
gtkdocize=/bin/true \
autoreconf ...
but that doesn't get me much further -
autoreconf: running: gtkdocize --copy
Can't exec "gtkdocize": No such file or directory at
/usr/share/autoconf/Autom4te/FileUtils.pm line 293.
autoreconf: error: gtkdocize failed with exit status: 2
That line is just a generic 'report that a command failed' line, I
cannot see where gtkdocize is being invoked.
Since I think that installing gtkdoc for this is an unnecessary
overhead, I'm halting this build, and everything that depended on it
(biber, possibly looking at biber deps, reviewing xfce-4.16 for my
own use. Unless someone has an easy solution, the only thing I'll
be monitoring is firefox.
Perhaps, if there is no solution, I will bring forward itstool and
Pygments, and grudgingly install gtk-doc (I already have all of
docbook), but this overhead *really* pisses me off and I'm not in
any hurry to go back to installing gtk-doc which in my experience
makes builds take even longer when it is present.
Or perhaps the days of a somewhat minimal LFS are gone, and
gtkdocize and its deps needs to be in LFS ? That would certainly be
a much bigger LFS.
More generally, it does seem that BLFS is more often broken these
days.
Fortunately, I'm still in chroot on my latest build, so I can
continue to use the system and my browsers - this is another example
of why I now prefer to build (at least) Xorg and firefox in chroot
(on sysv).
Sadly, I'm thinking about giving this up.
ĸen
--
(The Balancing Monks) use small brass weights, none of them bigger
than a fist. They work. Well, obviously they work. The world has not
tipped up yet. -- The Thief Of Time
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
