From: klarasm <klarasm@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] ghostscript does not include cups device support on armv6-musl and probably others
Date: Tue, 05 May 2020 22:19:06 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21662@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2139 bytes --]
New issue by klarasm on void-packages repository
https://github.com/void-linux/void-packages/issues/21662
Description:
I discovered this when trying to set up a print server on a Raspberry PI 1 model B. Cups complains of `unknown device: cups` It seems that ghostscript is not built with cups device support, as can be seen below.
Using `xbps-query ghostscript` on my x86_64 desktop system shlib-requires include `libcups.so.2` which is not included on the Raspberry Pi. I compiled ghostscript for x86_64, x86_64-musl, armv6l, armv6l-musl, aarch64, aarch64-musl and only the x86_64 version seems to link to `libcups.so.2`. I have posted the results of xbps-query on ghostscript for the targets below.
I also included the build log for armv6l-musl and the log for the failed cups job.
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname: `Void 4.19.115_1 armv6l-musl Unknown uptodate rrnFFF`
* package: ghostscript-9.52_1 cups-2.3.1_1 (indirectly)
### Expected behavior
Executed on a x86_64 desktop:
```
$ gs -h | grep cups
chp2200 cif cljet5 cljet5c cljet5pr coslw2p coslwxl cups declj250 deskjet
$ echo $?
0
$
```
### Actual behavior
Executed on a Raspberry Pi 1 model B
```
$ gs -h | grep cups
$ echo $?
1
$
```
### Steps to reproduce the behavior
Install ghostscript and execute `gs -h | grep cups` on Raspberry Pi 1 model B.
### Attached files
```
$ for i in x86_64 x86_64-musl armv6l armv6l-musl aarch64 aarch64-musl; do XBPS_ARCH=$i xbps-query -Ri --repository=. ghostscript;
```
[xbps-query-ghostscript.txt](https://github.com/void-linux/void-packages/files/4583308/xbps-query-ghostscript.txt)
```
$ ./xbps-src pkg ghostscript 2>&1 > build-ghostcript_armv6-musl.log
```
[build-ghostcript_armv6-musl.log](https://github.com/void-linux/void-packages/files/4583359/build-ghostcript_armv6-musl.log)
```
# cat error_log | grep Job\ 6
```
[cups-error.log](https://github.com/void-linux/void-packages/files/4583416/cups-error.log)
next reply other threads:[~2020-05-05 20:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 20:19 klarasm [this message]
2020-05-06 4:23 ` ericonr
2020-05-06 13:44 ` klarasm
2020-05-06 19:17 ` ericonr
2020-05-07 0:29 ` klarasm
2020-05-07 0:34 ` klarasm
2020-05-07 16:07 ` klarasm
2020-05-07 16:10 ` klarasm
2020-05-07 16:14 ` klarasm
2020-05-07 16:32 ` klarasm
2020-05-07 16:39 ` klarasm
2020-05-07 16:39 ` klarasm
2020-05-07 17:20 ` klarasm
2020-05-07 17:25 ` klarasm
2020-05-07 18:02 ` klarasm
2020-05-07 18:02 ` [ISSUE] [CLOSED] " klarasm
2020-05-07 18:21 ` klarasm
2020-05-08 4:25 ` fosslinux
2020-05-09 11:42 ` klarasm
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21662@inbox.vuxu.org \
--to=klarasm@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).