From: Juergen Beisert <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: David Thomas <david.thomas@ggtg.net>
Subject: Re: [ptxdist] [PATCH 3/3] Rules to build ghostscript for the host.
Date: Wed, 5 Mar 2014 09:57:06 +0100 [thread overview]
Message-ID: <201403050957.06958.jbe@pengutronix.de> (raw)
In-Reply-To: <63F3A45AB9EA8943A92845E4748C0F4B010E563E@exchange-server.intranet.ggtg.net>
Hi David,
welcome to the printing hell :)
I also tried with CUPS and Ghostscript. Its far from perfect, but it seems to
work. The CUPS project is not interested in cross compiling (there was a
statement at one of their mailing lists longer time ago and their buildsystem
is really broken regarding this) and the Ghostscript buildsystem is an ugly
mixture of autotools based configure and hand made Makefiles. A real mess. I'm
using Ghostscript 8.70. Should I send my variant as well?
Regards,
Juergen
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-03-05 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 15:40 David Thomas
2014-03-05 8:57 ` Juergen Beisert [this message]
2014-03-05 9:08 ` Alexander Aring
2014-03-05 10:03 ` [ptxdist] FW: " David Thomas
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=201403050957.06958.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=david.thomas@ggtg.net \
--cc=ptxdist@pengutronix.de \
/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