From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [scarthgap][PATCH 2/2] ghostscript: fix build with gcc-15 on host
Date: Tue, 28 Apr 2026 09:57:02 +0300 [thread overview]
Message-ID: <afBaPjcuxdcaXR-0@nuoska> (raw)
In-Reply-To: <CA+chaQfN=O1YD0C03ZL-gKLzG+B7sHXzJ4Sx-eLfY5Q3CyEOGg@mail.gmail.com>
Hi,
On Tue, Apr 28, 2026 at 08:52:37AM +0200, Martin Jansa wrote:
> On Tue, Apr 28, 2026 at 8:46 AM Mikko Rapeli <mikko.rapeli@linaro.org> wrote:
> >
> > From: Martin Jansa <martin.jansa@gmail.com>
> >
> > (From OE-Core rev: 02e282f6417274a93c6f01978bf33e2d171297b0)
> >
> > Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
> > ---
> > ...Fix-compatibility-with-C23-compilers.patch | 67 +++++++++++++++++++
> > .../ghostscript/ghostscript_10.05.1.bb | 4 +-
> > 2 files changed, 68 insertions(+), 3 deletions(-)
> > create mode 100644 meta/recipes-extended/ghostscript/ghostscript/0001-Bug-708160-Fix-compatibility-with-C23-compilers.patch
> ...
> > diff --git a/meta/recipes-extended/ghostscript/ghostscript_10.05.1.bb b/meta/recipes-extended/ghostscript/ghostscript_10.05.1.bb
> > index 57a1098521..8f132d55c6 100644
> > --- a/meta/recipes-extended/ghostscript/ghostscript_10.05.1.bb
> > +++ b/meta/recipes-extended/ghostscript/ghostscript_10.05.1.bb
> > @@ -25,9 +25,7 @@ def gs_verdir(v):
> > SRC_URI = "https://github.com/ArtifexSoftware/ghostpdl-downloads/releases/download/gs${@gs_verdir("${PV}")}/${BPN}-${PV}.tar.gz \
> > file://ghostscript-9.16-Werror-return-type.patch \
> > file://avoid-host-contamination.patch \
> > - file://CVE-2025-59798.patch \
> > - file://CVE-2025-59799.patch \
> > - file://CVE-2025-59800.patch \
> > + file://0001-Bug-708160-Fix-compatibility-with-C23-compilers.patch \
> > "
>
> This part doesn't look right, did you remove CVE patches by accident
> when resolving conflict?
Thanks! Completely wrong conflict resolution. Need more coffee...
Cheers,
-Mikko
prev parent reply other threads:[~2026-04-28 6:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 6:43 [scarthgap][PATCH 1/2] ghostscript: Pin to C17 std Mikko Rapeli
2026-04-28 6:43 ` [scarthgap][PATCH 2/2] ghostscript: fix build with gcc-15 on host Mikko Rapeli
2026-04-28 6:52 ` Martin Jansa
2026-04-28 6:57 ` Mikko Rapeli [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=afBaPjcuxdcaXR-0@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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