Getting failures trying to build glib from git
Stephen Oberholtzer
stevie at qrpff.net
Mon Mar 20 22:38:55 UTC 2017
Greetings,
(Note: I am not subscribed to the list, so please be sure to Reply-All)
I'm trying to track down a strange issue reported against irssi (#856201)
which appears to be introduced by some change in glib.
By pulling versions from snapshots.debian,org, I was able to determine that
the problem did not exist in 2.49.2-2, but it did exist in 2.49.3-1.
My next step was to bisect 2.49.2
(b990acf7ae7cfd6dec5c7de61de49e45d6112af9) and 2.49.3
(8d68a27f7055eb80cde6d4ac67e0dce751522b05). I started by cloning glib. I
then checked out the 2.49.2 tag and copied the 'debian' directory from
2.49.2-2. Unfortunately, this is not working out as well as I would have
liked; I'm getting build errors when I use dpkg-buildpackage -uc -us -B to
try to build the code.
Specifically, I get a failure about a missing "README" file:
Makefile.am: installing './INSTALL'
Makefile.am: error: required file './README' not found
(many warnings about 'source file is in a subdirectory, but option
subdir-objects is disabled)
autoreconf: automake failed with exit status: 1
dh_autoreconf: autoreconf -f -i returned exit code 1
/usr/share/cdbs/1/rules/autoreconf.mk:10: recipe for target
'debian/autoreconf.after' failed
make: *** [debian/autoreconf.after] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
I don't have this issue when I just manually run "./autogen.sh && make -s".
I tried just manually running ./autogen.sh, but then dpkg-buildpackage
balks and insists that I distclean first.
What do I need to do to be able to bisect the upstream code?
--
-- Stevie-O
Real programmers use COPY CON PROGRAM.EXE
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20170320/f88f32ee/attachment.html>
More information about the pkg-gnome-maintainers
mailing list