All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: Andrea Parri <andrea.parri@amarulasolutions.com>
Cc: "Paul E. McKenney" <paulmck@linux.ibm.com>,
	perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: perfbook
Date: Sat, 27 Oct 2018 22:27:24 +0900	[thread overview]
Message-ID: <6f0b596f-82df-6778-4d2b-26010d135901@gmail.com> (raw)
In-Reply-To: <20181027125844.GA6083@andrea>

On 2018/10/27 21:58, Andrea Parri wrote:
>> Just want to make sure the gs version.
>>
>> "gs -v" on my Ubuntu 18.04 says:
>>
>> GPL Ghostscript 9.25 (2018-09-13)
>> Copyright (C) 2018 Artifex Software, Inc.  All rights reserved.
>>
>> What does your "gs -v" say?
> 
> It said:
> 
> GPL Ghostscript GIT PRERELEASE 9.25 (2018-03-21)
> Copyright (C) 2018 Artifex Software, Inc.  All rights reserved.
> 
> which suggested that my previous "from ubuntu 18.04" was in fact not
> matching reality: it looks like I installed gs from sources, only a
> few months ago, and completely forgot about it. ;/  Mah, 

Ah!

>                                                          I manually
> removed my binary (/usr/local/bin/gs), and apt-purged-and-installed
> fig2ps ghostscript ghostscript-x gv.
> 
> 
> Now it says:
> 
> GPL Ghostscript 9.25 (2018-09-13)
> Copyright (C) 2018 Artifex Software, Inc.  All rights reserved.
> 
> which seems to match what you reported above.  I was then able to
> generate perfbook.pdf, even though with a bunch of:
> 
> CodeSamples/SMPdesign/smpalloc.canonical.eps --> CodeSamples/SMPdesign/smpalloc.canonical.pdf
> GPL Ghostscript 9.25: Unrecoverable error, exit code 1
That's why the output of e2ping is redirected to /dev/null in the Makefile.

> 
> I only had a quick look at the generated .pdf, but I haven't noticed
> issues.  Are those errors expected?  Any other suggestion?

As I mentioned earlier, the error message from gs is
expected and can be safely ignored for perfbook.pdf generation.
Please restore Makefile by "git checkout -- Makefile".

Glad to know you can now build .pdf on your own.

And if you will ever do the first-time build again, you can do
parallel make by saying "make -j4" (4 is for a quad-core machine).

You can try it by "make neatfreak; make -j4" if you'd like to.

        Thanks, Akira

> 
> Thanks,
>   Andrea
> 
> 
>>
>>         Akira


  reply	other threads:[~2018-10-27 22:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181025083609.GA6766@andrea>
     [not found] ` <20181025100235.GR4170@linux.ibm.com>
2018-10-26 20:20   ` perfbook Andrea Parri
2018-10-26 21:02     ` perfbook Akira Yokosawa
2018-10-26 22:14       ` perfbook Andrea Parri
2018-10-26 22:45         ` perfbook Akira Yokosawa
2018-10-26 23:06           ` perfbook Andrea Parri
2018-10-26 23:43             ` perfbook Akira Yokosawa
2018-10-27  0:33               ` perfbook Akira Yokosawa
2018-10-27  0:43                 ` perfbook Andrea Parri
2018-10-27  1:57                   ` perfbook Paul E. McKenney
2018-10-27 10:11                   ` perfbook Akira Yokosawa
2018-10-27  3:50         ` perfbook Akira Yokosawa
2018-10-27 12:58           ` perfbook Andrea Parri
2018-10-27 13:27             ` Akira Yokosawa [this message]
2018-10-27 17:09             ` perfbook Paul E. McKenney

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=6f0b596f-82df-6778-4d2b-26010d135901@gmail.com \
    --to=akiyks@gmail.com \
    --cc=andrea.parri@amarulasolutions.com \
    --cc=paulmck@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.