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: Mon, 24 Oct 2016 11:33:30 +0200 [thread overview]
Message-ID: <83690cb5-5fcc-2d96-09f9-233da2ebe936@atsonline.de> (raw)
In-Reply-To: <20161021152416.onw7sxcgngslzbge@pengutronix.de>
On 21/10/16 05:24 PM, Michael Olbrich wrote:
> On Fri, Oct 21, 2016 at 12:41:48PM +0200, Andreas Geisenhainer wrote:
>> On 21/10/16 11:28 AM, Michael Olbrich wrote:
>>> On Fri, Oct 21, 2016 at 10:26:37AM +0200, Andreas Geisenhainer wrote:
>>>> $(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.
> I just wanted to be sure. This options exists if the configure script was
> generated with newer autoconf versions.
You're right, again. Some update with my system allows me to
reproduce the behavior where the configure switch appears again.
As of now, I'm unable to determine the difference between the
autoconf versions on my main system and our build system/ptxdist.
All seem to use 2.69.
Let's just put this patch on the back burner for a bit …
At least we are aware of some problems, who might need some
attention down the line …
have a nice day
Andreas
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-10-24 9:33 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
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 [this message]
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=83690cb5-5fcc-2d96-09f9-233da2ebe936@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