From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14976] New: Ghostscript package can not process pdf files anymore
Date: Mon, 29 Aug 2022 04:53:18 +0000 [thread overview]
Message-ID: <bug-14976-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=14976
Bug ID: 14976
Summary: Ghostscript package can not process pdf files anymore
Product: buildroot
Version: 2022.02
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: lars.george@biotronik.com
CC: buildroot@uclibc.org
Target Milestone: ---
Dear Buildroot Dev Team,
thanks for the great work in the first place!
I am facing an issue with the Ghostscript package that is available in
buildroot. Starting with Version 2022.02 I am not able to process PDF files
anymore. I was already in contact with the Ghostscript developers, and we found
out that this has to do with the added compile option "--without-pdf" as the
version was updated to 9.55.0
(https://github.com/buildroot/buildroot/commit/7a4944569ce83b0b7b0cabd6e8aa184b8cb72a22).
They changed how PDF files are processed and did a greater rework, but adding
this above mentioned option totally disables the PDF feature (which is crucial
for example when driverless printing via Ghostscript is used). I think this is
not a generally wanted option. They also offered help when further need is
required to work out the proper compile options for the make settings within
buildroot.
--
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
next reply other threads:[~2022-08-29 4:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 4:53 bugzilla [this message]
2022-08-30 5:25 ` [Buildroot] [Bug 14976] Ghostscript package can not process pdf files anymore bugzilla
2024-06-15 15:03 ` 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@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