Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: audit: update to 3.0
Date: Sat, 03 Apr 2021 05:31:19 +0200	[thread overview]
Message-ID: <20210403033119.-i2I2XAgCLrk5NWIsi1BfgPipaYBc_rqPFyGLSqM4YQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28447@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 4144 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/pull/28447#issuecomment-812803391

Comment:
Having fixed that, there's still a failure here which I don't understand, but it also happens in previous versions, so not holding back for it:

```
make  auparse_test auparselol_test lookup_test \
  auparse_test.py
make[4]: Entering directory '/builddir/audit-3.0.1/auparse/test'
cc -DHAVE_CONFIG_H -I. -I../..  -I../../auparse -I../../lib   -fstack-clash-protection -D_FORTIFY_SOURCE=2 -mtune=generic -O2 -pipe    -MT auparse_test.o -MD -MP -MF .deps/auparse_test.Tpo -c -o auparse_test.o auparse_test.c
mv -f .deps/auparse_test.Tpo .deps/auparse_test.Po
/bin/sh ../../libtool  --tag=CC   --mode=link cc  -fstack-clash-protection -D_FORTIFY_SOURCE=2 -mtune=generic -O2 -pipe    -static -Wl,-z,relro -Wl,-z,now -Wl,--as-needed     -o auparse_test auparse_test.o ../../auparse/libauparse.la ../../lib/libaudit.la ../../common/libaucommon.la
libtool: link: cc -fstack-clash-protection -D_FORTIFY_SOURCE=2 -mtune=generic -O2 -pipe -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o auparse_test auparse_test.o  ../../auparse/.libs/libauparse.a /builddir/audit-3.0.1/lib/.libs/libaudit.a ../../lib/.libs/libaudit.a -lcap-ng ../../common/.libs/libaucommon.a
cc -DHAVE_CONFIG_H -I. -I../..  -I../../auparse -I../../lib   -fstack-clash-protection -D_FORTIFY_SOURCE=2 -mtune=generic -O2 -pipe    -MT auparselol_test.o -MD -MP -MF .deps/auparselol_test.Tpo -c -o auparselol_test.o auparselol_test.c
mv -f .deps/auparselol_test.Tpo .deps/auparselol_test.Po
/bin/sh ../../libtool  --tag=CC   --mode=link cc  -fstack-clash-protection -D_FORTIFY_SOURCE=2 -mtune=generic -O2 -pipe    -static -Wl,-z,relro -Wl,-z,now -Wl,--as-needed     -o auparselol_test auparselol_test.o ../../auparse/libauparse.la ../../lib/libaudit.la ../../common/libaucommon.la
libtool: link: cc -fstack-clash-protection -D_FORTIFY_SOURCE=2 -mtune=generic -O2 -pipe -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o auparselol_test auparselol_test.o  ../../auparse/.libs/libauparse.a /builddir/audit-3.0.1/lib/.libs/libaudit.a ../../lib/.libs/libaudit.a -lcap-ng ../../common/.libs/libaucommon.a
cc -DHAVE_CONFIG_H -I. -I../..  -I../../auparse -I../../lib   -fstack-clash-protection -D_FORTIFY_SOURCE=2 -mtune=generic -O2 -pipe    -MT lookup_test.o -MD -MP -MF .deps/lookup_test.Tpo -c -o lookup_test.o lookup_test.c
mv -f .deps/lookup_test.Tpo .deps/lookup_test.Po
/bin/sh ../../libtool  --tag=CC   --mode=link cc  -fstack-clash-protection -D_FORTIFY_SOURCE=2 -mtune=generic -O2 -pipe     -Wl,-z,relro -Wl,-z,now -Wl,--as-needed     -o lookup_test lookup_test.o ../../auparse/libauparse.la ../../lib/libaudit.la ../../common/libaucommon.la
libtool: link: cc -fstack-clash-protection -D_FORTIFY_SOURCE=2 -mtune=generic -O2 -pipe -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/lookup_test lookup_test.o  ../../auparse/.libs/libauparse.so /builddir/audit-3.0.1/lib/.libs/libaudit.so ../../lib/.libs/libaudit.so -lcap-ng ../../common/.libs/libaucommon.a
make[4]: Nothing to be done for 'auparse_test.py'.
make[4]: Leaving directory '/builddir/audit-3.0.1/auparse/test'
make  check-local
make[4]: Entering directory '/builddir/audit-3.0.1/auparse/test'
test "../.." = "../.." || \
                cp ../../auparse/test/test*.log .
LC_ALL=C \
./auparse_test > auparse_test.cur
Config file /etc/audit/auditd.conf doesn't exist, skipping
make[4]: *** [Makefile:708: check-local] Error 1
make[4]: Leaving directory '/builddir/audit-3.0.1/auparse/test'
make[3]: *** [Makefile:579: check-am] Error 2
make[3]: Leaving directory '/builddir/audit-3.0.1/auparse/test'
make[2]: *** [Makefile:2038: check-recursive] Error 1
make[2]: Leaving directory '/builddir/audit-3.0.1/auparse'
make[1]: *** [Makefile:2190: check] Error 2
make[1]: Leaving directory '/builddir/audit-3.0.1/auparse'
make: *** [Makefile:465: check-recursive] Error 1
=> ERROR: audit-3.0.1_1: do_check: '${make_cmd} ${make_check_args} ${make_check_target}' exited with 2
=> ERROR:   in do_check() at common/build-style/gnu-configure.sh:33
```

  parent reply	other threads:[~2021-04-03  3:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03 19:35 [PR PATCH] " paper42
2021-02-03 19:52 ` ericonr
2021-02-10  1:13 ` ericonr
2021-02-10  1:13 ` ericonr
2021-02-10 10:01 ` paper42
2021-02-10 13:33 ` ericonr
2021-02-10 15:21 ` paper42
2021-02-15 17:19 ` ericonr
2021-02-15 17:21 ` ericonr
2021-02-15 20:46 ` paper42
2021-02-15 20:46 ` [PR PATCH] [Updated] " paper42
2021-04-03  3:31 ` ericonr [this message]
2021-04-03  3:32 ` [PR PATCH] [Closed]: " ericonr

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=20210403033119.-i2I2XAgCLrk5NWIsi1BfgPipaYBc_rqPFyGLSqM4YQ@z \
    --to=ericonr@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).