public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Hsia-Jun Li" <randy.li@synaptics.com>
To: openembedded-core@lists.openembedded.org
Cc: "Hsia-Jun(Randy) Li" <randy.li@synaptics.com>
Subject: [PATCH 0/2] [WIP]: fix build failure caused by zstd
Date: Mon, 30 Aug 2021 18:46:42 +0800	[thread overview]
Message-ID: <20210830104644.422663-1-randy.li@synaptics.com> (raw)

From: "Hsia-Jun(Randy) Li" <randy.li@synaptics.com>

The configure script of some packages may not be able to
handle this correctly.

I have not verified all the packages, I was developing
something for meta-clang actually.

Hsia-Jun(Randy) Li (2):
  curl: fix the dependency to zstd
  gcc: disable zstd by default

 meta/recipes-devtools/gcc/gcc-11.2.inc   | 2 ++
 meta/recipes-support/curl/curl_7.78.0.bb | 1 +
 2 files changed, 3 insertions(+)

-- 
2.7.4


             reply	other threads:[~2021-08-30 10:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30 10:46 Hsia-Jun Li [this message]
2021-08-30 10:46 ` [PATCH 1/2] curl: fix the dependency to zstd Hsia-Jun Li
2021-08-30 10:46 ` [PATCH 2/2] gcc: disable zstd by default Hsia-Jun Li
2021-08-30 16:02   ` [OE-core] " Khem Raj

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=20210830104644.422663-1-randy.li@synaptics.com \
    --to=randy.li@synaptics.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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