From: Andreas Geisenhainer <Andreas.Geisenhainer@atsonline.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] updates lighttpd version 1.4.39 -> 1.4.42
Date: Fri, 21 Oct 2016 12:41:48 +0200 [thread overview]
Message-ID: <4fe11615-44b5-1766-1529-6fe955bcb970@atsonline.de> (raw)
In-Reply-To: <20161021092807.he73yp4jdzqergnw@pengutronix.de>
On 21/10/16 11:28 AM, Michael Olbrich wrote:
> On Fri, Oct 21, 2016 at 10:26:37AM +0200, Andreas Geisenhainer wrote:
>> -config LIGHTTPD_MEMCACHE
>> +config LIGHTTPD_MEMCACHED
> This deserves entry in scripts/migrate/migrate_ptx to help migration. There
> should be enough examples show how it works if you are unfamiliar with sed
> scripts.
I'll look into it. Thanks for the pointer.
Should the migration from->to be based on the current->next
release?
>
>> $(CROSS_AUTOCONF_USR) \
>> - --runstatedir=/run \
> Are you sure this option is gone?
About 95.8201%. The option is no longer listed in ./configure
and it explicitly complains about it, and fails, when set.
>
>> + --without-openssl \
> This is wrong. It's already set based on PTXCONF_LIGHTTPD_OPENSSL above.
> You might want to move that line if the order in './configure --help'
> changed.
You're right, my bad.
Have a nice Weekend
Andreas
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-10-21 10:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 8:26 Andreas Geisenhainer
2016-10-21 9:28 ` Michael Olbrich
2016-10-21 10:41 ` Andreas Geisenhainer [this message]
2016-10-21 11:59 ` Clemens Gruber
2016-10-21 15:25 ` Michael Olbrich
2016-10-21 15:24 ` Michael Olbrich
2016-10-24 9:33 ` Andreas Geisenhainer
2016-10-24 11:48 ` Michael Olbrich
2016-10-24 13:21 ` Andreas Geisenhainer
2016-10-21 10:05 ` Alexander Dahl
2016-10-31 14:16 ` Alexander Dahl
2016-10-31 15:14 ` Clemens Gruber
2016-11-11 9:23 ` 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=4fe11615-44b5-1766-1529-6fe955bcb970@atsonline.de \
--to=andreas.geisenhainer@atsonline.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