configure.in checks for some hard-coded library names and then gives up. Should be relatively easy to fix. Or notify upstream and have fix that ancient configure.in.
I think I've got this fixed. Best to leave the bug open until the final 1.5.0 is out. I didn't find any run-time problems yet but I might have been doing it wrong. Patch sent upstream.
No, that didn't go in. Working on a new patch.
pmacct already failed to compile against ~dev-libs/mongo-c-driver-0.7.1 but is also incompatible with >=dev-libs/mongo-c-driver-0.98.0. Patching isn't trivial.
Hello, just tried dropping these ancient mongo-c-driver versions and found that pmacct still depends on <dev-libs/mongo-c-driver-0.98. Would it be possible to migrate to some newer version please?
Latest 1.7.0 fails :( checking whether to enable PostgreSQL support... no checking whether to enable MongoDB support... yes checking for MONGODB... no checking default locations for libmongoc... not found checking for mongo_connect in -lmongoc... no configure: error: ERROR: missing MongoDB library (0.8 version). Refer to: https://github.com/mongodb/mongo-c-driver-legacy !!! Please attach the following file when seeking support: !!! /var/tmp/portage/net-analyzer/pmacct-1.7.0-r1/work/pmacct-1.7.0/config.log * ERROR: net-analyzer/pmacct-1.7.0-r1::local failed (configure phase):
(In reply to Tomáš Mózes from comment #5) > Latest 1.7.0 fails :( Yes, this is one of the side effects of drive-by feature development by third parties. pmacct developers included but never maintained the new feature.
(In reply to Jeroen Roovers from comment #6) > Yes, this is one of the side effects of drive-by feature development by > third parties. pmacct developers included but never maintained the new > feature. https://github.com/pmacct/pmacct/issues/187#issuecomment-370160483 Seems like the maintainers will remove mongodb, maybe we should drop the mongodb USE flag?
(In reply to Tomáš Mózes from comment #7) > (In reply to Jeroen Roovers from comment #6) > > Yes, this is one of the side effects of drive-by feature development by > > third parties. pmacct developers included but never maintained the new > > feature. > > https://github.com/pmacct/pmacct/issues/187#issuecomment-370160483 > > Seems like the maintainers will remove mongodb, That's not exactly how I read it. "Slowly phase out" it says. > maybe we should drop the > mongodb USE flag? We might be interested to learn how they intend to slowly phase out mongodb support. Dropping it prematurely doesn't make sense.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e675b02c805b83f5226422ad79796490b7334fd4 commit e675b02c805b83f5226422ad79796490b7334fd4 Author: Jeroen Roovers <jer@gentoo.org> AuthorDate: 2020-07-22 05:33:11 +0000 Commit: Jeroen Roovers <jer@gentoo.org> CommitDate: 2020-07-22 06:07:48 +0000 net-analyzer/pmacct: Version 1.7.5 - Drop IUSE=mongodb Package-Manager: Portage-3.0.0, Repoman-2.3.23 Closes: https://bugs.gentoo.org/518624 Closes: https://bugs.gentoo.org/664504 Signed-off-by: Jeroen Roovers <jer@gentoo.org> net-analyzer/pmacct/Manifest | 1 + net-analyzer/pmacct/pmacct-1.7.5.ebuild | 95 +++++++++++++++++++++++++++++++++ 2 files changed, 96 insertions(+)
