All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/xerces: drop patch
Date: Wed, 22 Feb 2023 22:00:45 +0100	[thread overview]
Message-ID: <20230222220045.5508e055@windsurf> (raw)
In-Reply-To: <20230222181254.2533041-1-fontaine.fabrice@gmail.com>

On Wed, 22 Feb 2023 19:12:54 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> Drop patch which is not needed since commit
> 62cab101356c97432da482e168adaf065de65c4f. This patch is actually raising
> a build failure since bump to version 3.2.4 in commit
> d2d8f146a9f0ed3b66c4dd470bb76efdbb630a75 and
> https://github.com/apache/xerces-c/commit/af1935b567c18c8b2de71d6ea97239be60876335:
> 
> CMake Error at src/CMakeLists.txt:1271 (add_library):
>   Target "xerces-c" links to target "CURL::libcurl" but the target was not
>   found.  Perhaps a find_package() call is missing for an IMPORTED target, or
>   an ALIAS target is missing?
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/c62856a5eeb34714f26235b2d6f8adc4ea612686
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  .../0001-fix-static-linking-with-curl.patch   | 39 -------------------
>  1 file changed, 39 deletions(-)
>  delete mode 100644 package/xerces/0001-fix-static-linking-with-curl.patch

Applied to master, thanks.

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

      reply	other threads:[~2023-02-22 21:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 18:12 [Buildroot] [PATCH 1/1] package/xerces: drop patch Fabrice Fontaine
2023-02-22 21:00 ` 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=20230222220045.5508e055@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=thomas.petazzoni@bootlin.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.