Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/2] libkrb5: New package
Date: Tue, 21 Nov 2017 13:56:22 +0100	[thread overview]
Message-ID: <20171121135622.033678af@windsurf.lan> (raw)
In-Reply-To: <1511213549-1878-1-git-send-email-nerv@dawncrow.de>

Hello,

Thanks for this new iteration. Much better without the
configure.ac patch.

On Mon, 20 Nov 2017 22:32:28 +0100, Andr? Hentschel wrote:

> +LIBKRB5_VERSION = 1.15.2
> +LIBKRB5_SITE = https://web.mit.edu/kerberos/dist/krb5/1.15
> +LIBKRB5_SOURCE = krb5-$(LIBKRB5_VERSION).tar.gz
> +LIBKRB5_SUBDIR = src
> +LIBKRB5_LICENSE = MIT
> +LIBKRB5_LICENSE_FILES = NOTICE
> +LIBKRB5_INSTALL_STAGING = YES
> +LIBKRB5_AUTORECONF = YES

Are you sure you still need to AUTORECONF the package? Now that the
configure.ac patch is gone, I don't think this is necessary anymore.

> +# Add sane assumptions about cross-compiling

Rather than "sane assumptions", a clearer comment would be: "The
configure script uses AC_TRY_RUN tests to check for those values, which
doesn't work in a cross-compilation scenario. Therefore, we feed the
configure script with the correct answer for those tests". Or something
along those lines.

Note: both issues can be fixed when applying, no need to resend just
for that.

Thanks!

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

  parent reply	other threads:[~2017-11-21 12:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 21:32 [Buildroot] [PATCH v4 1/2] libkrb5: New package André Hentschel
2017-11-20 21:32 ` [Buildroot] [PATCH v4 2/2] squid: Add optional dependency on libkrb5 André Hentschel
2017-11-21 12:56 ` Thomas Petazzoni [this message]
2017-11-21 17:21   ` [Buildroot] [PATCH v4 1/2] libkrb5: New package André Hentschel
2017-11-23 20:25 ` 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=20171121135622.033678af@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