From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Andreas Ziegler <br015@umbiko.net>
Cc: "Romain Naour" <romain.naour@gmail.com>,
"Jörg Krause" <joerg.krause@embedded.rocks>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/zziplib: fix static build failure with mpd
Date: Fri, 24 Dec 2021 18:22:28 +0100 [thread overview]
Message-ID: <20211224182228.70f47125@windsurf> (raw)
In-Reply-To: <20211224162152.1035557-1-br015@umbiko.net>
Hello Andreas,
On Fri, 24 Dec 2021 17:21:52 +0100
Andreas Ziegler <br015@umbiko.net> wrote:
> The latest released version of zziplib copies static libraries with appended
> major version, but omits creating the necessary links to the base file names.
> This prevents the linker to find the libraries via the search path.
>
> There is a discussion upstream: https://github.com/gdraheim/zziplib/issues/117
>
> Update zzip/CMakeLists.txt to the current master, version a32538e to enable
> creation of symlinks.
>
> This resolves the following autobuild issue:
>
> http://autobuild.buildroot.net/results/ba711034c0abe980f677e26de41739223e2f66e9
>
> Signed-off-by: Andreas Ziegler <br015@umbiko.net>
> ---
> ...01-update-zzip-cmakelists-to-a32538e.patch | 220 ++++++++++++++++++
> 1 file changed, 220 insertions(+)
> create mode 100644 package/zziplib/0001-update-zzip-cmakelists-to-a32538e.patch
>
> diff --git a/package/zziplib/0001-update-zzip-cmakelists-to-a32538e.patch b/package/zziplib/0001-update-zzip-cmakelists-to-a32538e.patch
> new file mode 100644
> index 0000000000..1ed9243f69
> --- /dev/null
> +++ b/package/zziplib/0001-update-zzip-cmakelists-to-a32538e.patch
> @@ -0,0 +1,220 @@
> +--- zziplib-0.13.72/zzip/CMakeLists.txt
> ++++ zziplib-a32538e/zzip/CMakeLists.txt
Thanks a lot for looking into this build issue!
However, we want patches to have a proper description and
Signed-off-by. But it's not really nice to just have a large patch that
updates file XYZ to version ABC. What about backporting the few
specific patches that are needed?
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
next prev parent reply other threads:[~2021-12-24 17:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 16:21 [Buildroot] [PATCH 1/1] package/zziplib: fix static build failure with mpd Andreas Ziegler
2021-12-24 17:22 ` Thomas Petazzoni [this message]
2021-12-27 7:40 ` [Buildroot] [PATCH v2 " Andreas Ziegler
2022-03-20 11:41 ` [Buildroot] [PATCH v3 " Andreas Ziegler
2022-03-27 15:57 ` Arnout Vandecappelle
2022-03-30 19:43 ` Peter Korsgaard
2022-07-25 20:49 ` Arnout Vandecappelle
2022-07-26 6:24 ` Andreas Ziegler
2022-07-28 14:36 ` Andreas Ziegler
2022-07-29 9:13 ` [Buildroot] [PATCH 1/1] package/zziplib: create symlinks only if target is missing Andreas Ziegler
2022-07-29 9:34 ` Andreas Ziegler
2022-07-29 16:37 ` [Buildroot] [PATCH v2 " Andreas Ziegler
2022-07-29 20:15 ` Arnout Vandecappelle
2022-09-13 14:18 ` Peter Korsgaard
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=20211224182228.70f47125@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=br015@umbiko.net \
--cc=buildroot@buildroot.org \
--cc=joerg.krause@embedded.rocks \
--cc=romain.naour@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