public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12661] cups problems in buildroot
Date: Thu, 23 Apr 2020 06:43:06 +0000	[thread overview]
Message-ID: <bug-12661-163-bI7UqmJyB4@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12661-163@https.bugs.busybox.net/>

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

--- Comment #3 from Alexey <skif@skif-web.ru> ---
I found the answer myself

It's big complex ptobleb with qpdf, cups-filters and ghostscrips
patchs sumbitted:

http://lists.busybox.net/pipermail/buildroot/2020-April/279672.html
http://lists.busybox.net/pipermail/buildroot/2020-April/279676.html
http://lists.busybox.net/pipermail/buildroot/2020-April/279677.html
http://lists.busybox.net/pipermail/buildroot/2020-April/279673.html

There are multiple issues in buildroot that faults cups printing.

First trouble is incorrect qpdf buiding.
Qpdf is mandatory dependence of cups.
In current master, qpdf builds with incorrect --no-random option. On 
any work< qpdf send 'no such file' error. For example:
qpdf /usr/share/cups/data/secret.pdf -

This commmand must get PDF file in stdout.But only 'No such file or
 directory' error present.

0/1 patch fix this by changing configure options to 
with-random=/dev/random.

Next global problem - cups-filters need ghostscript.
From  https://github.com/OpenPrinting/cups-filters/blob/master/README :
By default, pdftops uses Ghostscript if this does not get changed
    at compile time, for example by the Linux distribution vendor.

0/2 patch fix id by settinbg ghostscript as default render if 
ghostscript enabled in voard config.

Last trouble - ghostscript building without cups support.

0/3 patch fix is by removing disable-patch option. Now, if cups is 
enabled, it will be added to dependencies and correct configure 
options added to ghostscript building. Also fixed ghostscript 
buildroot building issue with unpleasant hack in configure.ac, which 
broke pkg-config. It's broke cups search by ghostscript configure 
script.
GHOSTSCRIPT_CUPS_CONFIG_FIX also needed for this task.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-04-23  6:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 15:16 [Buildroot] [Bug 12661] New: cups problems in buildroot bugzilla at busybox.net
2020-03-18 19:30 ` [Buildroot] [Bug 12661] " bugzilla at busybox.net
2020-03-18 19:43 ` bugzilla at busybox.net
2020-04-23  6:43 ` bugzilla at busybox.net [this message]
2020-05-18  5:25 ` bugzilla at busybox.net

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-12661-163-bI7UqmJyB4@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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