Re: [Pan-users] Any hope to get a fix for uutomake 1.13.x support ?

[Duncan]

fredbezies posted on Tue, 12 Feb 2013 21:53:13 +0100 as excerpted:

> Sorry to "spam" the list, but I opened a bug related to automake 1.13.x.
> 
> See https://bugzilla.gnome.org/show_bug.cgi?id=693371
> 
> Thanks for any infos related to this bug fixing !

FWIW, I run gentoo here (based on the bug you're on arch), and build pan 
live-git from sources using a live-ebuild script.

The thing is, building from live-git is a bit more complex than the 
typical tarball build, because you're building from "raw" sources, not 
from an already configured-for-shipping tarball.   Various source files 
have been updated, but .configure itself hasn't been.  Part of the 
process of preparing a versioned tarball includes running a selection of 
"autotools" that make sure everything's updated, in order, and when you 
fetch and build from live-git, that hasn't been done, so you need to do 
the prepping yourself.

Try this and see if it works.  Before .configure, run the following (this 
is cribbed from gentoo's live-build ebuild for git-pan):

intltoolize --force --automake

autoreconf --force

Assuming nothing goes wrong... NOW try the usual .configure and build 
from there, and see if it goes better. =:^)


Some additional notes, FWTW...

Gentoo actually "slots" its automake, along with autoconf, etc, so more 
than one version can be installed at a time.  There's then a wrapper 
script that detects what version was used to create the shipped files and 
normally uses the same version to rebuild, altho a different version can 
be forced.  For automake, line one of the shipped Makefile.in should be a 
comment that states what version of automake was used to create it; the 
automake wrapper checks that and invokes the same version, 1.11, 1.13, 
etc, when doing that step of the autoreconf.  To force a specific 
version, WANT_AUTOMAKE=1.13 (or similar) can be set.  In the case of pan, 
automake-1.11 is what the first line of Makefile.in says generated it, so 
the wrapper will try to use automake-1.11 to regenerate it as well.  But 
I tried setting WANT_AUTOMAKE=1.13, and while the newer automake did 
output a couple warnings about deprecated input files being used, it 
still worked.  So it should work for you as well, hopefully...

autoreconf is is actually a metatool that calls a bunch of other tools 
(autoconf, autoheader, aclocal, automake/gettextize, libtoolize) each in 
turn.  You can look at its manpage and those of the individual tools it 
invokes, if you're curious or if something goes wrong and you want to try 
to work around it.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman