linux/poky.git/meta/recipes-extended/ghostscript/ghostscript_9.05.bb, branch pyro

ghostscript: upgrade to 9.07

2013-06-25T16:44:59+00:00

Remove unuseful patch: * 0001-make-ghostscript-work-with-long-building-directory.patch Port applicable patches: * ghostscript-9.02-genarch.patch * ghostscript-9.02-parallel-make.patch * ghostscript-9.02-prevent_recompiling.patch * ghostscript-9.05-NOT-check-endian.patch * ghostscript-native-fix-disable-system-libtiff.patch (From OE-Core rev: aea8f29275fd7c2341c429b46c25e17afe532b3e) Signed-off-by: Wenzong Fan Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

ghostscript: fix endianness detection

2013-02-08T14:50:37+00:00

[ CQID: WIND00394747 ] The original patch removes endianness detection completely, causing lcms to be built against the wrong endian. Instead, pass the correct endian through the recipe using SITEINFO_ENDIANNESS. (From OE-Core rev: 0a07ec7d13becc7ce87c502e75a006300a7090a5) Signed-off-by: Jesse Zhang Signed-off-by: Robert Yang Signed-off-by: Mark Hatle Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

ghostscript-native:fix host underlinking issues

2012-12-17T17:24:54+00:00

The ghostscript-native will check libtiff automatically at configure time and libtiff needs libjpeg. If libtiff and libjpeg is just populated to staging native directories and the host doesn't install them, the libjpeg could not be linked, fail with: |libjpeg.so.8, needed by libtiff.so, not found |libtiff.so: undefined reference to `jpeg_set_defaults@LIBJPEG_8.0' |collect2: error: ld returned 1 exit status Disable libtiff support to fix this issue and modify configure to let disable system libtiff could work. We also explicity disable fontconfig, freetype, cups for ghostscript-native to avoid the similar issues. [YOCTO #3562] (From OE-Core rev: c00778dd0d9c3b62657057e92c868ad2257d72d3) Signed-off-by: Hongxu Jia Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

ghostscript: make ghostscript work with long building path

2012-12-03T14:32:43+00:00

If TMPDIR has more than 256 chars, building ghostscript fails. This violates the 410 length limit of TMPDIR. This patch makes building ghostscript succeed by changing its MAX_TOKEN from 256 to 512. [YOCTO #2766] (From OE-Core rev: 30a19b7c791abcbf09193c678866df66d470a6d9) Signed-off-by: Chen Qi Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

recipes-extended: replace virtclass-native(sdk) with class-native(sdk)

2012-11-02T16:18:29+00:00

The overrides virtclass-native and virtclass-nativesdk are deprecated, which should be replaced by class-native and class-nativesdk. [YOCTO #3297] (From OE-Core rev: 528b4ab831c7b0bc1412318d29e2b7f9cf711d57) Signed-off-by: Robert Yang Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

ghostscript: disable libidn support

2012-09-04T11:53:11+00:00

If libidn is just populated to sysroot but rpm packages are not created, build ghostscript will check libidn automatically and then depends on libidn. But package libidn doesn't exist, so build image which contains ghostscript will fail with: | error: Failed dependencies: | libidn11 >= 1.25 is needed by ghostscript-9.05-r2.i586 | libidn.so.11(LIBIDN_1.0) is needed by ghostscript-9.05-r2.i586 | libidn.so.11 is needed by ghostscript-9.05-r2.i586 Disable libidn support to fix this issue. (From OE-Core rev: 509eb624c89249ff169de24fed448e8d7894a6f6) Signed-off-by: Kang Kai Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

ghostscript: Fix remaining CP_ prallel make races

2012-03-29T08:44:46+00:00

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

ghostscript: Fixes for parallel_make

2012-03-28T15:53:08+00:00

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

ghostscript: fix typo in packaging

2012-03-19T14:37:44+00:00

(From OE-Core rev: 410784aa6ed80a26d1f2cff1219548909af87cff) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

ghostscript: Fix patch related build issues

2012-03-15T00:11:40+00:00

The file ${S}/configure.ac is a symlink which seems to confuse some patch application tools but not in all cases. Whilst I'd love to understand why there is a difference, this fixes the build failures by applying the patch to the real file rather than the symlink. (From OE-Core rev: 34f3127bac9e5a15c33d21a6a6ac83c6060dcac9) Signed-off-by: Richard Purdie