public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Slawek Lis" <slis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/suricata/
Date: Mon, 28 Dec 2015 05:49:35 +0000 (UTC)	[thread overview]
Message-ID: <1451281944.f0be13e9ed39aba8138a9d7842745d08f837415f.slis@gentoo> (raw)

commit:     f0be13e9ed39aba8138a9d7842745d08f837415f
Author:     Slawomir Lis <slis <AT> gentoo <DOT> org>
AuthorDate: Mon Dec 28 05:52:24 2015 +0000
Commit:     Slawek Lis <slis <AT> gentoo <DOT> org>
CommitDate: Mon Dec 28 05:52:24 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f0be13e9

Fixed #569636

Package-Manager: portage-2.2.26

 net-analyzer/suricata/suricata-2.0.10.ebuild | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/net-analyzer/suricata/suricata-2.0.10.ebuild b/net-analyzer/suricata/suricata-2.0.10.ebuild
index 40b2740..3c69998 100644
--- a/net-analyzer/suricata/suricata-2.0.10.ebuild
+++ b/net-analyzer/suricata/suricata-2.0.10.ebuild
@@ -96,7 +96,8 @@ src_configure() {
 		myeconfargs+=( $(use_enable luajit) )
 	fi
 
-	LIBS+="-lrt -lnuma"
+# this should be used when pf_ring use flag support will be added
+# 	LIBS+="-lrt -lnuma"
 
 	econf LIBS="${LIBS}" ${myeconfargs[@]}
 }


             reply	other threads:[~2015-12-28  5:49 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-28  5:49 Slawek Lis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-12-28  5:53 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/suricata/ Slawek Lis
2016-02-19  5:32 Slawek Lis
2016-02-19  5:59 Slawek Lis
2016-02-19 20:19 Slawek Lis
2016-04-26  6:18 Slawek Lis
2016-06-29  6:44 Slawek Lis
2016-06-30 19:03 Slawek Lis
2016-10-10 19:08 Slawek Lis
2016-11-29 12:05 Slawek Lis
2016-12-15  6:19 Slawek Lis
2016-12-28 13:25 Slawek Lis
2017-01-07 10:25 Slawek Lis
2017-07-24  8:30 Slawek Lis
2018-01-23  9:15 Slawek Lis
2018-01-24  7:00 Slawek Lis
2018-03-26 19:33 Michał Górny
2018-05-11  7:43 Slawek Lis
2018-06-03 13:49 Aaron Bauman
2018-06-11 14:04 Marek Szuba
2019-09-08 19:25 Slawek Lis
2019-12-16 16:05 Marek Szuba
2019-12-19 15:18 Marek Szuba
2019-12-20 10:18 Marek Szuba
2020-02-05 15:30 Marek Szuba
2020-03-04  9:46 Marek Szuba
2020-04-23 21:11 Marek Szuba
2020-04-23 21:11 Marek Szuba
2020-05-22 21:02 Marek Szuba
2020-07-17 20:10 Marek Szuba
2020-10-09 11:41 Marek Szuba
2020-10-14 14:44 Marek Szuba
2020-12-03 12:54 Marek Szuba
2020-12-06 22:02 Marek Szuba
2021-01-25 17:38 Marek Szuba
2021-01-25 17:38 Marek Szuba
2021-03-04 14:47 Marek Szuba
2021-03-04 14:47 Marek Szuba
2021-04-03 19:53 Sam James
2021-05-17 16:15 Marek Szuba
2021-06-21 14:54 Marek Szuba
2021-06-21 14:54 Marek Szuba
2021-06-21 16:03 Marek Szuba
2021-07-01  9:47 Marek Szuba
2021-07-01  9:47 Marek Szuba
2021-07-25 20:58 Marek Szuba
2021-08-23 21:29 Marek Szuba
2021-09-03 12:15 Marek Szuba
2021-09-03 12:15 Marek Szuba
2021-09-25 19:08 Sam James
2021-11-19 14:59 Marek Szuba
2021-11-19 14:59 Marek Szuba
2022-03-23  1:24 Sam James
2022-04-25 22:57 Marek Szuba
2022-04-25 22:57 Marek Szuba
2022-07-13 15:55 Marek Szuba
2022-07-13 15:55 Marek Szuba
2022-07-27 23:54 Marek Szuba
2022-08-24 15:36 Marek Szuba
2022-08-24 15:36 Marek Szuba
2022-09-01 12:27 Marek Szuba
2022-10-04  0:53 Marek Szuba
2022-11-01  0:36 Marek Szuba
2022-11-01 13:10 Marek Szuba
2022-11-10  0:42 Marek Szuba
2022-12-02 10:00 Marek Szuba
2023-02-01 10:51 Marek Szuba
2023-02-01 10:51 Marek Szuba
2023-03-01 23:12 Marek Szuba
2023-03-22 23:43 Marek Szuba
2023-04-16 20:03 Marek Szuba
2023-05-11 12:03 Marek Szuba
2023-06-27 21:56 Marek Szuba
2023-08-16 17:08 Marek Szuba
2023-08-16 17:08 Marek Szuba
2023-10-25 22:04 Marek Szuba
2023-10-25 22:04 Marek Szuba
2023-11-29 21:16 Petr Vaněk
2024-01-23  5:07 Ionen Wolkens
2024-04-07  1:06 Marek Szuba
2024-11-09 13:54 Sam James

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=1451281944.f0be13e9ed39aba8138a9d7842745d08f837415f.slis@gentoo \
    --to=slis@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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