All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 1/2] package/libssh2: Update to newest version
Date: Wed, 1 Nov 2017 10:58:23 +0100	[thread overview]
Message-ID: <20171101105823.6128ce6b@windsurf> (raw)
In-Reply-To: <1509472591-12650-1-git-send-email-sam.voss@rockwellcollins.com>

Hello,

On Tue, 31 Oct 2017 12:56:30 -0500, Sam Voss wrote:
> Update libssh2 to use the newest version from git. This caused a
> transition from released version number to hash as it has not been
> version rev'd in over a year (see issue
> https://github.com/libssh2/libssh2/issues/220 for bump request).
> 
> This brings in changes to the autoconf to correctly pick the crypto
> library.
> 
> Signed-off-by: Sam Voss <sam.voss@rockwellcollins.com>

I've applied, thanks! See a few comments/questions below.

> diff --git a/package/libssh2/0001-drop-custom-buildconf-script.patch b/package/libssh2/0001-drop-custom-buildconf-script.patch
> new file mode 100644
> index 0000000..a9a98e0
> --- /dev/null
> +++ b/package/libssh2/0001-drop-custom-buildconf-script.patch
> @@ -0,0 +1,121 @@
> +From 39a2a444a32896bd2dab37c9b247ccfd11ff4693 Mon Sep 17 00:00:00 2001
> +From: "Yann E. MORIN" <yann.morin.1998@free.fr>
> +Date: Mon, 30 Oct 2017 19:29:12 +0100
> +Subject: [PATCH] buildsystem: drop custom buildconf script, rely on autoreconf
> +
> +The buildconf script is currently required, because we need to copy a
> +header around, because it is used both from the library and the examples
> +sources.
> +
> +However, having a custom 'buildconf'-like script is not needed if we can
> +ensure that the header / exists by the time it is needed. For That, we
> +can just append the src/ directory to the headers search path for the
> +examples.
> +
> +And then it means we no longer need to generate the same header twice,
> +so we remove the second one from configure.ac.
> +
> +Now, we can just call "autoreconf -fi" to generate the autotools files,
> +instead of relying on the canned sequence in "buildconf", since
> +autoreconf has now long known what to do at the correct moment (future
> +versions of autotools, automake, autopoint, autoheader etc... may
> +require an other ordering, or other intermediate steps, etc...).
> +
> +Eventually, get rid of buildconf now it is no longer needed. In fact, we
> +really keep it for legacy, but have it just call autoreconf (and print a
> +nice user-friendly warning).
> +
> +Update gitignore accordingly, too.
> +
> +Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> +Cc: Sam Voss <sam.voss@rockwellcollins.com>

Has this patch been submitted upstream?


> +# autoreconf must be ran when building off git, as it has not been ran at hash
> +LIBSSH2_AUTORECONF = YES

"it has not been ran at hash" doesn't make much sense. I've simplified
the whole comment to "building from a git clone".

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2017-11-01  9:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 17:56 [Buildroot] [PATCH v5 1/2] package/libssh2: Update to newest version Sam Voss
2017-10-31 17:56 ` [Buildroot] [PATCH v5 2/2] package/libssh2: Add selectable crypto libraries Sam Voss
2017-11-01 15:15   ` Yann E. MORIN
2017-11-01  9:58 ` Thomas Petazzoni [this message]
2017-11-01 14:54   ` [Buildroot] [PATCH v5 1/2] package/libssh2: Update to newest version Sam Voss

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=20171101105823.6128ce6b@windsurf \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.