mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Bruno Thomsen <bruno.thomsen@gmail.com>
To: ptxdist@pengutronix.de
Cc: chf.fritz@googlemail.com, m.olbrich@pengutronix.de,
	Bruno Thomsen <bruno.thomsen@gmail.com>
Subject: [ptxdist] [PATCH 2/2] strongswan: remove staging
Date: Tue, 29 May 2018 17:01:48 +0200	[thread overview]
Message-ID: <20180529150148.30456-3-bruno.thomsen@gmail.com> (raw)
In-Reply-To: <20180529150148.30456-1-bruno.thomsen@gmail.com>

strongswan now compiles with gcc 7.3.1 from OSELAS.Toolchain 2018.02.0.

Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
---
 rules/strongswan.in | 8 +-------
 1 file changed, 1 insertion(+), 7 deletions(-)

diff --git a/rules/strongswan.in b/rules/strongswan.in
index f7ed103e2..e45a95f74 100644
--- a/rules/strongswan.in
+++ b/rules/strongswan.in
@@ -1,6 +1,4 @@
-## SECTION=staging
-## old section:
-### SECTION=networking
+## SECTION=networking
 
 menuconfig STRONGSWAN
 	bool
@@ -15,10 +13,6 @@ menuconfig STRONGSWAN
 	  strongSwan's needs. See 'Required Kernel Modules' here:
 	  http://wiki.strongswan.org/projects/strongswan/wiki/KernelModules
 
-	  STAGING: remove in ptxdist-2019.04.0
-	  Old version that fails to build gcc 7.x. should be updated to a
-	  new version.
-
 if STRONGSWAN
 
 config STRONGSWAN_LIBCURL
-- 
2.17.0


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      parent reply	other threads:[~2018-05-29 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29 15:01 [ptxdist] [PATCH 0/2] Strongswan is alive Bruno Thomsen
2018-05-29 15:01 ` [ptxdist] [PATCH 1/2] strongswan: version bump 5.3.5 -> 5.6.1 Bruno Thomsen
2018-05-29 15:01 ` Bruno Thomsen [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=20180529150148.30456-3-bruno.thomsen@gmail.com \
    --to=bruno.thomsen@gmail.com \
    --cc=chf.fritz@googlemail.com \
    --cc=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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