All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: "Александр Демидов" <demidov@dimti.ru>
Subject: Re: undefined reference to `capng_save_state' - linkink e4rat-collect
Date: Mon, 26 Sep 2016 15:50:14 -0400	[thread overview]
Message-ID: <2940705.f4qkhcR1aB@x2> (raw)
In-Reply-To: <fbf5d55e86089f990d55a8118884cc36@dimti.ru>

On Monday, September 26, 2016 4:17:24 PM EDT Александр Демидов wrote:
> Hello
> 
> I try to use new applications for me - e4rat
> 
> My OS: ArchLinux
> 
> I install audit with static libs for resolve building e4rat application
> 
> But, in building e4rat-collect, i fetched error:
> 
> [ 52%] Linking CXX executable ../e4rat-collect
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.2.1/../../../../lib/libaudit.a(libaudit.o
> ): In function `audit_can_control':
> (.text+0x25f6): undefined reference to `capng_save_state'
> 
> I see in https://svn.fedorahosted.org/svn/audit/trunk/lib/libaudit.c the
> code
> 
> int audit_can_control(void)
> {
> #ifdef HAVE_LIBCAP_NG
>  void *state = capng_save_state();
> 
> But i dont understand, where error. In audit or in e4rat?
> If that error - bug in e4rat
> (https://wiki.archlinux.org/index.php/E4rat), please tell and i wrote to
> developers e4rat, if autdi is clean.

I think that you'll need static libcap-ng libraries to link against also. Or 
you can compile audit without libcap-ng support.

-Steve


--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit

      reply	other threads:[~2016-09-26 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-26 13:17 undefined reference to `capng_save_state' - linkink e4rat-collect Александр Демидов
2016-09-26 19:50 ` Steve Grubb [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2940705.f4qkhcR1aB@x2 \
    --to=sgrubb@redhat.com \
    --cc=demidov@dimti.ru \
    --cc=linux-audit@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.