Bug #2646: rudder-agent is missing a build dependency on tokyo cabinet - Rudder - Issue Tracker

Actions

Copy link

Bug #2646

closed

rudder-agent is missing a build dependency on tokyo cabinet

Added by Michael Gliwinski over 12 years ago. Updated almost 10 years ago.

Status:

Rejected

Priority:

N/A

Assignee:

Michael Gliwinski

Category:

Packaging

Target version:

Pull Request:

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

This is actually a dependency of the bundled CFEngine.

The exact package name is tokyocabinet-devel for RHEL and libtokyocabinet-dev for Debian.

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Jonathan CLARKE over 12 years ago

Status changed from New to Discussion
Assignee changed from Jonathan CLARKE to Michael Gliwinski

Hi Michael,

Thanks for the bug report. Actually, rudder-agent still uses BerkeleyDB as a backend for CFEngine, since we're having difficulties finding the right packages on all supported OSes. Migration to CFEngine 3.3 (or higher) is currently planned in Rudder 2.6, thus using TokyoCabinet, for now.

Have you actually encountered something that didn't work because of this?

Actions

Copy link

Updated by Michael Gliwinski over 12 years ago

Sorry, yes I got an error from configure which stopped rpmbuild, and I knew CFEngine switched from BDB to TokyoCabinet, so I thought it's a missing dep. But this would explain other problems I'm having with this build. Anyway, the error was:

...
checking for tchdbnew in -ltokyocabinet... no
configure: error: Cannot find Tokyo Cabinet
error: Bad exit status from /var/tmp/rpm-tmp.aKNg5L (%build)

RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.aKNg5L (%build)

I now checked the SOURCES/Makefile, but it says CFENGINE_RELEASE = 3.3.3.

The other problem I'm having is that after everything builds all CFEngine binaries are linked against libdb-4.3.so and I can't trace where this is coming from.

But then maybe the problem is that I'm using the wrong sources?

Actions

Copy link

Updated by Michael Gliwinski over 12 years ago

Michael Gliwinski wrote:

I now checked the SOURCES/Makefile, but it says CFENGINE_RELEASE = 3.3.3.

But then maybe the problem is that I'm using the wrong sources?

OK, never mind, I've now fetched rudder-packages repo again and I've seen a commit that reverts CFENGINE_RELEASE back to 3.2.4. With that everything built correctly (still had to use the QA_RPATHS=$[ 0x0020 ] workaround, as per my email to rudder-dev).

Actions

Copy link