linux/poky.git/meta/recipes-extended/ghostscript, branch master

The poky repository master branch is no longer being updated.

2025-11-07T13:31:53+00:00

You can either: a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs b) use the new bitbake-setup You can find information about either approach in our documentation: https://docs.yoctoproject.org/ Note that "poky" the distro setting is still available in meta-yocto as before and we continue to use and maintain that. Long live Poky! Some further information on the background of this change can be found in: https://lists.openembedded.org/g/openembedded-architecture/message/2179 Signed-off-by: Richard Purdie

ghostscript: Do not treat declaration-after-statement warning as error

2025-10-09T09:58:07+00:00

This option is added by ghostscript and is passed down to its modules e.g. brotli, brotli does expect c99 or newer standard and hence uses declarations after statement. This option causes compiler e.g. clang to find this warning and treat it as error on 32bit builds ./brotli/c/dec/decode.c:440:12: error: mixing declarations and code is incompatible with standards before C99 [-Werror,-Wdeclaration-after-statement] 440 | uint32_t __fastload_table = (*table); | ^ 1 error generated. (From OE-Core rev: 9b8e0b9a30f1de8bd1816f2528bc696f769dd8dc) Signed-off-by: Khem Raj Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

ghostscript: upgrade 10.05.1 -> 10.06.0

2025-10-02T10:28:03+00:00

Dropped 0001-Bug-708160-Fix-compatibility-with-C23-compilers.patch Added 0001-Fix-32-bit-build.patch to fix 32-bit archs build Added fPIC flag needed to prevent a linker error during the build process. This upgrade addresses CVEs: CVE-2025-59798, CVE-2025-59799, CVE-2025-59800, CVE-2025-59801 Changelog: https://ghostscript.readthedocs.io/en/gs10.06.0/News.html (From OE-Core rev: 0144e22195394ce2b21b476a1dcfde9129eaf615) Signed-off-by: Vijay Anusuri Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

recipes: cleanup CVE_STATUS which are resolved now

2025-08-28T09:47:08+00:00

The don't show up in CVE metrics anymore since they were either fixed upstream or recipe version was upgraded meanwhile. * bind CVE-2019-6470: cpe got corrected in nvd db * libxml2 CVE-2023-45322: version is now higher than NVD cpe * zlib CVE-2023-45853: version is now higher than NVD cpe * gcc CVE-2021-37322: version is now higher than NVD cpe * python3 * CVE-2007-4559: version is now higher than NVD cpe * CVE-2019-18348: version is now higher than NVD cpe * CVE-2020-15523: version is now higher than NVD cpe * CVE-2022-26488: version is now higher than NVD cpe * CVE-2015-20107: version is now higher than NVD cpe * CVE-2023-36632: version is now higher than NVD cpe * rust * CVE-2024-24576: NVD has no cpe, but we have newer version as fix * CVE-2024-43402: version is now higher than NVD cpe * cups CVE-2021-25317: version is now higher than NVD cpe * ghostscript CVE-2023-38559: version is now higher than NVD cpe * libtirpc CVE-2021-46828: version is now higher than NVD cpe * unzip CVE-2008-0888: version is now higher than NVD cpe * ffmpeg CVE-2023-39018: cpe got corrected in nvd db * libxslt CVE-2022-29824: version is now higher than NVD cpe * libyaml * CVE-2024-35325: CVE is now rejected in NVD DB * CVE-2024-35326: CVE is now rejected in NVD DB * CVE-2024-35328: CVE is now rejected in NVD DB Also add comment for iputils regarding reports for FKIE/NVD2. Also remove some trailing spaces in python recipe. (From OE-Core rev: 73ee9789183aa95072af2b51ac9e08203f4e33f9) Signed-off-by: Peter Marko Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

meta: remove consecutive blank lines

2025-06-20T11:07:27+00:00

Some of them were introduced by mass-removal of S = WORKDIR/git assignments; rather than try to fix up (or redo) just these, I've run this sed command over the whole tree: sed -i -z -E 's/([ \t\f\v\r]*\n){3,}/\n\n/g' `find . -name *.bb -o -name *.inc` The rationale is that more than one empty line is wasting vertical screen space, and does nothing for readability. (From OE-Core rev: cedc4ff7c9bcfb22a20e43e47f9759f4007a4f1a) Signed-off-by: Alexander Kanavin Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

ghostscript: Use TARGET_CFLAGS to pass compiler options

2025-06-09T16:43:41+00:00

Passing compiler options via CC is error prone when we allow toolchain selection. Use TARGET_CFLAGS instead. (From OE-Core rev: 2091ebf845004040a6227d18cfa6bb508d1b9c9f) Signed-off-by: Richard Purdie

ghostscript: upgrade 10.05.0 -> 10.05.1

2025-05-13T09:29:21+00:00

(From OE-Core rev: cc9ba7005fb155f4d5f2be9b23c12d14362a306b) Signed-off-by: Wang Mingyu Signed-off-by: Richard Purdie

ghostscript: fix build with gcc-15 on host

2025-04-29T08:55:31+00:00

(From OE-Core rev: 02e282f6417274a93c6f01978bf33e2d171297b0) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

ghostscript: Pin to C17 std

2025-03-27T11:19:04+00:00

The code defines a custom 'bool' type (as an 'int'), which is incompatible with C23 in which bool is a keyword, and trying to use fails because 'int' and 'bool' are used interchangeably in the code. Add the flag to CC variable, since CFLAGS is used by both c and c++ compilers and clang++ is less forgiving when C compiler only option is used on its cmdline so it complains about -std=gnu17 and bails out. (From OE-Core rev: 49657089ef215824f8f79a81deb7baf4f27d0030) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

ghostscript: upgrade 10.04.0 -> 10.05.0

2025-03-17T22:38:32+00:00

(From OE-Core rev: baef546edd9a719448cc39962dea24925aab70b8) Signed-off-by: Richard Purdie