From: klarasm <klarasm@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ghostscript does not include cups device support on armv6-musl and probably others
Date: Thu, 07 May 2020 20:21:36 +0200 [thread overview]
Message-ID: <20200507182136.iuNyAG268lYiZyFpXWLYEwfQr_VTGzDp_IkNFdsVCzY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21662@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1484 bytes --]
New comment by klarasm on void-packages repository
https://github.com/void-linux/void-packages/issues/21662#issuecomment-625419782
Comment:
(sorry for spamming, accidentally closed the issue earlier)
Ok, this is interesting. With the modified template the x86_64 Makefile also looks like this (seems I also missed an important line earlier):
```
# Define install location for 'cups' device/filter support
CUPSLIBS=
CUPSLIBDIRS=
CUPSSERVERBIN=
CUPSSERVERROOT=
CUPSDATA=
CUPSPDFTORASTER=0
SHARE_LCUPS=1
LCUPS_NAME=cups
LCUPSSRCDIR=
LCUPSBUILDTYPE=
CUPS_CC=$(CC)
SHARE_LCUPSI=1
LCUPSI_NAME=cupsimage
LCUPSISRCDIR=
CUPS_CC=$(CC)
CUPSCFLAGS= -DSHARE_LCUPS=$(SHARE_LCUPS) -DSHARE_LCUPSI=$(SHARE_LCUPSI)
```
With original template (x86_64):
```
# Define install location for 'cups' device/filter support
CUPSLIBS= cups
CUPSLIBDIRS=
CUPSSERVERBIN=/usr/lib/cups
CUPSSERVERROOT=/etc/cups
CUPSDATA=/usr/share/cups
CUPSPDFTORASTER=1
SHARE_LCUPS=1
LCUPS_NAME=cups
LCUPSSRCDIR=./cups
LCUPSBUILDTYPE=
CUPS_CC=$(CC)
SHARE_LCUPSI=1
LCUPSI_NAME=cupsimage
LCUPSISRCDIR=./cups
CUPS_CC=$(CC)
CUPSCFLAGS= -fstack-clash-protection -D_FORTIFY_SOURCE=2 -mtune=generic -O2 -pipe -DHAVE_RESTRICT=1 -DUSE_LIBPAPER -DSHARE_LCUPS=$(SHARE_LCUPS) -DSHARE_LCUPSI=$(SHARE_LCUPSI)
```
So it seems my change instead breaks build for x86_64 non-cross as well.
next prev parent reply other threads:[~2020-05-07 18:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 20:19 [ISSUE] " klarasm
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 [this message]
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=20200507182136.iuNyAG268lYiZyFpXWLYEwfQr_VTGzDp_IkNFdsVCzY@z \
--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).