Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: James Hilliard <james.hilliard1@gmail.com>,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4 1/2] package/libtirpc: Add optional GSSAPI support
Date: Sun, 25 Jul 2021 19:37:51 +0200	[thread overview]
Message-ID: <20210725193751.62d7666a@windsurf> (raw)
In-Reply-To: <6cd7e12d-3bcf-f177-650e-441f5a322e7c@mind.be>

On Sun, 25 Jul 2021 18:21:08 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:

>  Both applied to master, thanks.

Gah, I should have replied earlier. I didn't apply this because there
was a small issue, see below.

> > +config BR2_PACKAGE_LIBTIRPC_GSS
> > +	bool "gss"
> > +	depends on BR2_USE_MMU # libkrb5
> > +	depends on BR2_PACKAGE_LIBTIRPC
> > +	select BR2_PACKAGE_LIBKRB5

libkrb5 has a !BR2_STATIC_LIBS that is not taken into account here (and
the libtirpc main option does not have such a dependency).

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2021-07-25 17:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-18 20:44 [Buildroot] [PATCH v4 1/2] package/libtirpc: Add optional GSSAPI support James Hilliard
2021-07-18 20:44 ` [Buildroot] [PATCH v4 2/2] package/nfs-utils: Add optional GSS support James Hilliard
2021-07-21 20:40   ` Petr Vorel
2021-07-21 20:38 ` [Buildroot] [PATCH v4 1/2] package/libtirpc: Add optional GSSAPI support Petr Vorel
2021-07-25 16:21 ` Arnout Vandecappelle
2021-07-25 17:37   ` Thomas Petazzoni [this message]
2021-07-25 20:47     ` James Hilliard

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=20210725193751.62d7666a@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=james.hilliard1@gmail.com \
    /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