From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/ghostscript: new package
Date: Thu, 8 Dec 2016 23:06:06 +0100 [thread overview]
Message-ID: <20161208230606.64ce147c@free-electrons.com> (raw)
In-Reply-To: <20160912232623.1fc706be@free-electrons.com>
Hello,
On Mon, 12 Sep 2016 23:26:23 +0200, Thomas Petazzoni wrote:
> Since this mess of pre-defined per-architecture header files is really
> nasty, could you instead try to package the latest git version of
> ghostscript ?
>
> Indeed, since early July, the Git repository includes numerous
> cross-compilation fixes, and especially
> http://git.ghostscript.com/?p=user/chrisl/ghostpdl.git;a=commitdiff;h=0a44ce497dbf6064981d88953df63bfdfce0a984
> which generates the arch.h header using regular configure.ac tests.
>
> This should hopefully greatly simplify the whole problem.
>
> The libtiff directory problem has also been fixed by
> http://git.ghostscript.com/?p=user/chrisl/ghostpdl.git;a=commitdiff;h=3d3982f844fed6d6cb092055980900289fb6a402.
>
> But it's not clear which of these have landed in the main Ghostscript
> Git repository at http://git.ghostscript.com/?p=ghostpdl.git;a=summary,
> unfortunately.
>
> Could you have a look into this?
Could you please rework your patch to use the latest Git version of
ghostscript? It has commit
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=c3c4bf022a631be939ebb4bf6f59e41514cb1e48
which simplifies things a lot:
- No need to build host-ghostscript
- No need for hardcoded architecture headers
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-12-08 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 20:36 [Buildroot] [PATCH 1/1] package/ghostscript: new package Bernd Kuhls
2016-09-12 21:26 ` Thomas Petazzoni
2016-12-08 22:06 ` Thomas Petazzoni [this message]
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=20161208230606.64ce147c@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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