From: "'Angelo Machils' via voidlinux" <voidlinux@googlegroups.com>
To: voidlinux@googlegroups.com
Subject: Re: LibreSwan?
Date: Wed, 26 Jun 2019 09:01:39 +0300 [thread overview]
Message-ID: <20190626060139.plu2wh6ug6iz7nv7@am-mini> (raw)
Hello,
Yes, I did see that one could disable certain options in a config file,
but even when I comment out the part for SElinux, the compile still
fails because the applications wants at least the libseliux-devel
libraries.
Regards,
Angelo Machils
On 19/06/25 10:20PM, Cameron Nemo wrote:
> On Tue, Jun 25, 2019 at 10:14 PM 'Angelo Machils' via voidlinux
> <voidlinux@googlegroups.com> wrote:
> >
> > Hello,
> >
> > Since for some reason StrongSwan doesn't seem to work with our
> > corporate
> > VPN setup (not just in VOID, I're heard these report from users of
> > other
> > distros as well), I wanted to compile LibreSwan and I manage to
> > solve
> > most of the dependencies, but the SElinux (yes, I know) dependency
> > I'm
> > not able to solve. Did anyone manage to successfully compile
> > LibreSwan
> > and/or is it possible to have it in the default repositories?
> >
>
> Do you have a draft template? Usually there is a build option to
> disable SELinux integration.
>
> Regards,
> --
> Cameron Nemo
--
You received this message because you are subscribed to the Google Groups "voidlinux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voidlinux+unsubscribe@googlegroups.com.
To post to this group, send email to voidlinux@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/20190626060139.plu2wh6ug6iz7nv7%40am-mini.
For more options, visit https://groups.google.com/d/optout.
next reply other threads:[~2019-06-26 6:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 6:01 'Angelo Machils' via voidlinux [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-26 5:14 LibreSwan? 'Angelo Machils' via voidlinux
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=20190626060139.plu2wh6ug6iz7nv7@am-mini \
--to=voidlinux@googlegroups.com \
--cc=angelo@machils.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).