Re: [ANNOUNCE] Pan release 0.150

Duncan <[email protected]>
Newsgroups gmane.comp.gnome.apps.pan.user
Message-ID <[email protected]>
Dominique Dumont posted on Fri, 04 Mar 2022 14:27:34 +0100 as excerpted:

> On Wednesday, 2 March 2022 21:27:57 CET Duncan wrote:
>> My autotools foo isn't the best so I'm not entirely sure this answers 
your question, but...
>> 
>> ./configure [snipped as it's repeated below]
> 
> ./configure is not archived in git repo, (although I think a new
> configure script is provided in the tarballs available on
> pan.rebelbase).
> 
> If you're compiling from git, you should regenerate this script by
> running something like:
> 
> ./autogen.sh --with-gnutls --with-dbus --with-gmime-crypto
> --with-gtkspell -- enable-libnotify --enable-gkr --enable-manual
> 
> Running this script requires that automake tools (or may be autotools)
> are installed on your system. A package for automake should be available
> on gentoo

Thanks for your patience.

Generally on gentoo, autoconf and automake are both considered toolchain 
utilities installed on most (all?) build systems[1].  In fact, multiple 
versions may be installed on systems that build packages incompatible with 
the current latest autoconf/automake versions (stable or ~arch aka 
testing), latest being the default.  The tooling/scripts generally detect 
when .configure is outdated or missing and run the associated tools as 
necessary.

Here's a somewhat longer excerpt from the build, previous to 
the .configure command I posted.  (Space-edited for posting.  The e-prefix 
is common for gentoo specific tools, here wrappers for autoreconf and 
libtoolize.)  I don't see autogen.sh by name but I do see various other 
auto*.  FWIW there's a variable set in the ebuild that forces the full 
eautoreconf instead of just elibtoolize.  Does this look correct or do I 
need to dive further (do I need to see autogen.sh itself in the output)?

>>> Source unpacked in /tmp/portage/net-nntp/pan-9999/work
>>> Preparing source in /tmp/portage/net-nntp/pan-9999/work/pan-9999 ...
* =======================================================================
* Applying user patches from /etc/portage/patches ...
* Applying net-nntp.pan.smallish-10k.patch ...                      [ ok ]
* Applying net-nntp.pan.stacked-horizontal.patch ...                [ ok ]
* User patches applied.
* 
==========================================================================
* Disabling deprecation warnings ...                                [ ok ]
* Running eautoreconf in '/tmp/portage/net-nntp/pan-9999/work/
pan-9999' ...
* Running 'autopoint --force' ...                                   [ ok ]
* Running 'aclocal' ...                                             [ ok ]
* Running 'autoconf --force' ...                                    [ ok ]
* Running 'autoheader' ...                                          [ ok ]
* Running 'automake --add-missing --copy --foreign --force-
missing' ...                                                        [ ok ]
* Running elibtoolize in: pan-9999/
>>> Source prepared.
>>> Configuring source in /tmp/portage/net-nntp/pan-9999/work/pan-9999 ...
* econf: updating pan-9999/config.sub with /usr/share/gnuconfig/config.sub
* econf: updating pan-9999/config.guess with /usr/share/gnuconfig/
config.guess
./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-
linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/
usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-
tracking --disable-silent-rules --docdir=/usr/share/doc/pan-9999 --
htmldir=/usr/share/doc/pan-9999/html --libdir=/usr/lib64 --disable-
maintainer-mode --disable-nls --without-yelp-tools --without-webkit --
without-gmime-crypto --with-dbus --disable-gkr --with-gtkspell --disable-
libnotify --with-gnutls

---
[1]  Gentoo, or perhaps one should say portage, gentoo's default package-
manager, does have binpkgs, but with some exceptions they're generally 
only locally distributed.  Building from-source at the user end, tho not 
necessarily at the individual machine, is assumed, and while libs aren't 
split as they normally are on binary distros, build-deps are split from 
runtime-deps and build-time-only packages like automake/autoconf aren't 
normally required on non-build systems.

-- 
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


_______________________________________________
Pan-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/pan-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.