ancient: am I using it wrong?

Thanks for the update, I can see you’re shipping pkg-config file and library now:

# ancient -h
/usr/bin/ancient: error: '/usr/bin/.libs/ancient' does not exist
This script is just a wrapper for ancient.
See the libtool documentation for more information.
root@phd-sid:/var/www/debian/ancient/2022# dpkg -L ancient
/.
/usr
/usr/bin
/usr/bin/ancient
/usr/include
/usr/include/ancient
/usr/include/ancient/ancient.hpp
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libancient.a
/usr/lib/x86_64-linux-gnu/libancient.la
/usr/lib/x86_64-linux-gnu/libancient.so.2.0.0
/usr/lib/x86_64-linux-gnu/pkgconfig
/usr/lib/x86_64-linux-gnu/pkgconfig/libancient.pc
/usr/share
/usr/share/doc
/usr/share/doc/ancient
/usr/share/doc/ancient/LICENSE
/usr/share/doc/ancient/README.md.gz
/usr/share/doc/ancient/changelog.Debian.gz
/usr/share/doc/ancient/copyright
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/ancient.1.gz
/usr/lib/x86_64-linux-gnu/libancient.so
/usr/lib/x86_64-linux-gnu/libancient.so.2

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 19 (12 by maintainers)

Most upvoted comments

It probably also needs autoconf-archive (for AX_CXX_COMPILE_STDCXX).

manxorist on Aug 21, 2022

I installed debian & tools to try it myself, but unfortunately run into interesting set of issues.

If I use just the build files from the old one, I can produce a working .deb package - but it is still built with makefiles, no autoconfig there.

Since I’m still not an expert. Can you help me out here @alexmyczko Do you have your buildfiles somewhere I can try where this problem reproduces? But it looks like you got it already working. Now I’m just confused …

I do not think there ever was anything wrong with ancient in this regard. No need to try to reproduce anything. This was purely an issue on @alexmyczko 's side, and has already been confirmed so:

that was exactly it!

manxorist on Jan 14, 2022

I am really not an expert on (or have really any deeper knowledge at all about) debian packaging, but do you by any chance still have the file https://sources.debian.org/src/ancient/1.0-2/debian/install/ laying around in your updated debian packaging directory?

According to https://manpages.debian.org/testing/debhelper/dh_install.1.en.html it looks to me like it would, in addition to what make install installs, also install “ancient” from the current directory to"/usr/bin", which would overwrite the proper binary with whatever libtool had generated in the build directory.

I am a Debian user myself, so resolving any problems Debian has with packages that I am involved with has a high priority for me.

You might want to hold out a few days until https://github.com/temisu/ancient/issues/37 is resolved before releasing an updated package for ancient, though.

manxorist on Jan 12, 2022

I did contribute the pkg-config file as well as the autotools build system for ancient, but I am honestly not sure what could have gone wrong for you there.

I just did re-check the Automake file and did not spot anything obviously broken. I may of course have missed it.

For me, ./autogen.sh && ./configure && make && make install installs a proper binary.

If you are building that debian package yourself, can you provide a full build log?

manxorist on Jan 12, 2022