From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] openntpd: update to 6.2p3
Date: Wed, 22 Nov 2017 22:54:39 +0100 [thread overview]
Message-ID: <20171122225439.7b411286@windsurf.lan> (raw)
In-Reply-To: <20171120051147.qoedwxoxivo3encc@sapphire.tkos.co.il>
Hello,
On Mon, 20 Nov 2017 07:11:47 +0200, Baruch Siach wrote:
> > Still broken :\
>
> What is broken?
>
> I case AUTORECONF is still necessary even after the Makefile.am patch removal,
> the comment needs update.
Because our libtool patch doesn't apply to openntpd's ltmain.sh. So
I've kept the AUTORECONF = YES (after updating the comment, of course).
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-22 21:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 13:04 [Buildroot] [PATCH 1/2] openntpd: update to 6.2p3 Adam Duskett
2017-11-08 13:04 ` [Buildroot] [PATCH 2/2] openntpd: add check for LibreSSL Adam Duskett
2017-11-22 22:10 ` Thomas Petazzoni
2017-11-08 13:31 ` [Buildroot] [PATCH 1/2] openntpd: update to 6.2p3 Baruch Siach
2017-11-19 21:50 ` Adam Duskett
2017-11-20 5:11 ` Baruch Siach
2017-11-22 21:54 ` Thomas Petazzoni [this message]
2017-11-22 21:55 ` Thomas Petazzoni
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=20171122225439.7b411286@windsurf.lan \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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