mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Christoph Fritz <chf.fritz@googlemail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] strongswan: add package
Date: Wed, 06 Mar 2013 11:10:30 +0100	[thread overview]
Message-ID: <1362564630.3919.30.camel@mars> (raw)
In-Reply-To: <20130306082132.GH7949@pengutronix.de>

On Wed, 2013-03-06 at 09:21 +0100, Michael Olbrich wrote:
> On Tue, Mar 05, 2013 at 08:37:02PM +0100, Christoph Fritz wrote:
> > +# ----------------------------------------------------------------------------
> > +# Prepare
> > +# ----------------------------------------------------------------------------
> > +
> > +STRONGSWAN_CONF_TOOL	:= autoconf
> > +STRONGSWAN_CONF_OPT	:= \
> > +	$(CROSS_AUTOCONF_USR) \
> > +	--with-ipseclibdir=/usr/lib
> 
> I'm not sure if you misunderstood something, but I didn't mean that you
> should remove the configure options.

Thanks for the notice. I got you right. But v2 of this patch is no
"preliminary testing version" any more and the configure script is doing
a fine job with a good handful of plugins to connect to enough peer
configurations.
It's a bit versatile you may think, but this fits my needs best.

> You should explicitly specify all the options from the "Optional Features"
> section from "./configure --help".

And then comment out the ones which will never be used, either by
kconfig opt-in nor opt-out?

> A good starting point  usually is to add a kconfig options for all features
> that have external dependencies (don't forget the 'select' in
> strongswan.in) and choose a reasonable default for all others.

Let me reroll this.

> 
> It's also a good idea to run "readelf -d <binary>" to check if you missed
> any dependencies.

I already did this by using ldd.

Thanks
 -- Christoph



-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2013-03-06 10:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-20 21:22 [ptxdist] [PATCH] " Christoph Fritz
2013-03-04 17:04 ` Michael Olbrich
2013-03-05 19:37   ` [ptxdist] [PATCH v2] " Christoph Fritz
2013-03-06  8:21     ` Michael Olbrich
2013-03-06 10:10       ` Christoph Fritz [this message]
2013-03-06 12:50         ` Robert Schwebel
2013-03-06 22:54           ` [ptxdist] [PATCH v3] " Christoph Fritz
2013-03-20 11:44             ` Christoph Fritz
2013-03-20 13:49             ` Michael Olbrich
2013-03-26 11:21               ` [ptxdist] [PATCH v4] " Christoph Fritz
2013-03-27 18:10                 ` Michael Olbrich

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=1362564630.3919.30.camel@mars \
    --to=chf.fritz@googlemail.com \
    --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