From: Robert Schwebel <r.schwebel@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] strongswan: add package
Date: Wed, 6 Mar 2013 13:50:31 +0100 [thread overview]
Message-ID: <20130306125031.GW28383@pengutronix.de> (raw)
In-Reply-To: <1362564630.3919.30.camel@mars>
Hi Christoph,
On Wed, Mar 06, 2013 at 11:10:30AM +0100, Christoph Fritz wrote:
> > 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.
No :-)
> > 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?
No, but instead set them to the variant you have tested. The issue is
that, with a lot of configure options, not setting them explicitly means
that configure autodetects them. That may lead to different results,
i.e. based on the build order or other host influences. So you should
always specify all options - either according to the configuration, or
with a fixed value.
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-03-06 12:50 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
2013-03-06 12:50 ` Robert Schwebel [this message]
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=20130306125031.GW28383@pengutronix.de \
--to=r.schwebel@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