All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: TIAN Yuanhao <tianyuanhao3@163.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/gnutls: add patch to fix build failure
Date: Wed, 9 Oct 2024 23:23:04 +0200	[thread overview]
Message-ID: <20241009232304.71ef7b41@windsurf> (raw)
In-Reply-To: <20241009113410.5077-1-tianyuanhao3@163.com>

Hello,

On Wed,  9 Oct 2024 04:34:10 -0700
TIAN Yuanhao <tianyuanhao3@163.com> wrote:

> This patch needs to be applied before [1], otherwise it will cause the
> following build failure:

Could you then send both patches in a series?

> diff --git a/package/gnutls/0001-Fix-HAVE_LIBBROTLI_TRUE-and-HAVE_LIBZSTD_TRUE-value.patch b/package/gnutls/0001-Fix-HAVE_LIBBROTLI_TRUE-and-HAVE_LIBZSTD_TRUE-value.patch
> new file mode 100644
> index 0000000000..b389e387e4
> --- /dev/null
> +++ b/package/gnutls/0001-Fix-HAVE_LIBBROTLI_TRUE-and-HAVE_LIBZSTD_TRUE-value.patch
> @@ -0,0 +1,32 @@
> +Fix HAVE_LIBBROTLI_TRUE and HAVE_LIBZSTD_TRUE value
> +
> +"with_libbrotlienc", "with_libbrotlidec" and "with_libzstd" may be
> +empty, which is equivalent to "no".
> +
> +Signed-off-by: TIAN Yuanhao <tianyuanhao3@163.com>

If you run "make check-package", this should give you a warning that
you don't have an Upstream: tag. Has this patch been submitted
upstream? If not, you should do it. If yes, you should include an
Upstream: tag with a link to the upstream submission.

Thanks!

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

      reply	other threads:[~2024-10-09 21:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09 11:34 [Buildroot] [PATCH 1/1] package/gnutls: add patch to fix build failure TIAN Yuanhao
2024-10-09 21:23 ` Thomas Petazzoni via buildroot [this message]

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=20241009232304.71ef7b41@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=tianyuanhao3@163.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 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.