From: "Paul E. McKenney" <paulmck@kernel.org>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH -perfbook] epstopdf-rule.mk: Add -dNOSAFER to eps2eps for .eps -> .pdf (from .tex)
Date: Tue, 31 May 2022 21:48:00 -0700 [thread overview]
Message-ID: <20220601044800.GM1790663@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <6b69a285-0996-db50-d053-a402713e879c@gmail.com>
On Wed, Jun 01, 2022 at 08:25:31AM +0900, Akira Yokosawa wrote:
> Somehow, eps2eps doesn't have -dNOSAFER while epstopdf has
> --nosafer in the same recipe.
> On CentOS stream 8, ghostscript 9.27 complains about the lack of
> -dNOSAFER.
>
> Add the missing option.
>
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
Queued and pushed, thank you!
Thanx, Paul
> ---
> epstopdf-rule.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/epstopdf-rule.mk b/epstopdf-rule.mk
> index 4efad17a78a6..d248ce750d68 100644
> --- a/epstopdf-rule.mk
> +++ b/epstopdf-rule.mk
> @@ -28,7 +28,7 @@ ifeq ($(GS_953_OR_LATER),1)
> @eps2eps -dALLOWPSTRANSPARENCY $< $(basename $<)__.eps
> @epstopdf --gsopt=-dALLOWPSTRANSPARENCY $(GS_OPT) $(basename $<)__.eps $@
> else
> - @eps2eps $< $(basename $<)__.eps
> + @eps2eps -dNOSAFER $< $(basename $<)__.eps
> @epstopdf --nosafer $(GS_OPT) $(basename $<)__.eps $@
> endif
> @rm -f $(basename $<)__.eps
>
> base-commit: f19269d216ef6ebcfb417e87d040bd8374754c33
> --
> 2.25.1
>
prev parent reply other threads:[~2022-06-01 4:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 23:25 [PATCH -perfbook] epstopdf-rule.mk: Add -dNOSAFER to eps2eps for .eps -> .pdf (from .tex) Akira Yokosawa
2022-06-01 4:48 ` Paul E. McKenney [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=20220601044800.GM1790663@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=akiyks@gmail.com \
--cc=perfbook@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).