Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14976] Ghostscript package can not process pdf files anymore
Date: Tue, 30 Aug 2022 05:25:09 +0000	[thread overview]
Message-ID: <bug-14976-163-cVrte0Y80t@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14976-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=14976

--- Comment #1 from Lars <lars.george@biotronik.com> ---
I digged into the problem a little bit and got a fix for myself. First of all I
patched the mk file of the Ghostscript package:

 define GHOSTSCRIPT_REMOVE_LIBS
        rm -rf $(@D)/freetype $(@D)/ijs $(@D)/jbig2dec $(@D)/jpeg \
-               $(@D)/lcms2mt $(@D)/libpng $(@D)/openjpeg $(@D)/tiff \
+               $(@D)/lcms2mt $(@D)/libpng $(@D)/tiff \
                $(@D)/zlib
 endef
 GHOSTSCRIPT_POST_PATCH_HOOKS += GHOSTSCRIPT_REMOVE_LIBS
@@ -43,7 +43,7 @@
        --enable-freetype \
        --disable-gtk \
        --without-libpaper \
-       --without-pdf \
+       --with-pdf \
        --with-system-libtiff

 ifeq ($(BR2_PACKAGE_JBIG2DEC),y)


Furthermore I do need to have the following BR packages:
- BR2_PACKAGE_JBIG2DEC
- BR2_PACKAGE_OPENJPEG

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-08-30  5:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29  4:53 [Buildroot] [Bug 14976] New: Ghostscript package can not process pdf files anymore bugzilla
2022-08-30  5:25 ` bugzilla [this message]
2024-06-15 15:03 ` [Buildroot] [Bug 14976] " bugzilla

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=bug-14976-163-cVrte0Y80t@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.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