On 2018/10/27 02:43:19 +0200, Andrea Parri wrote:
> On Sat, Oct 27, 2018 at 09:33:57AM +0900, Akira Yokosawa wrote:
>> On 2018/10/27 8:43, Akira Yokosawa wrote:
>>> On 2018/10/27 8:06, Andrea Parri wrote:
>>>>> And you have a2ping 2.83p, right? Otherwise, Makefile should
>>>>> complain. Hmm???
>>>>
>>>> Indeed, 2.83p.
>>>>
>>>>
>>>>>
>>>>> Can you remove "> /dev/null 2>&1" on line 220 of Makefile,
>>>>> and let me know what a2ping should say?
>>>>
>>>> It says:
>>>>
>>>> /usr/local/bin/a2ping: not a GS output from gs (0)
>>>
>>> Umm, "gs (0)" suggests exit code of gs is 0, which should indicate
>>> success. I have no idea what is going on.
>>
>> Andrea,
>>
>> Do you happen to set some of environment variables:
>>
>> GS_OPTIONS
>> GS_DEVICE
>>
>> and the like?
>
> No GS_ variable set.
Hmm.
As a last resort, there are alternative commands to a2ping I'm aware of.
If "ps2epsi", "epstool", and "epstopdf" all work on your system,
I can provide a variant of Makefile which don't rely on a2ping.
How to check:
(You might need to install missing commands if any.)
$ ps2epsi SMPdesign/CPUvsEnet.eps /tmp/CPUvsEnet.epsi
$ epstool --copy --bbox --ignore-errors /tmp/CPUvsEnet.epsi /tmp/CPUvsEnet.epsij
$ cat /tmp/CPUvsEnet.epsij | epstopdf --filter --outfile=/tmp/CPUvsEnet.pdf
If /tmp/CPUvsEnet.pdf (Figure 6.12 in perfbook) is generated, those three
commands should be working properly.
I tried these commands this February when Fedora 28 updated Ghostscript to
9.22, and a2ping (2.77p) stopped working. Luckily, a2ping's maintainer
released 2.83p in March.
Thanks, Akira
>
> Andrea
>
>
>>
>> Akira
>>
>>>
>>> I have a Ubuntu 18.04 virtual machine and a2ping 2.83p works happily
>>> there.
>>>
>>> Sorry but I can't help you at the moment.
>>>
>>> Akira
>>>
>>>>
>>>> Andrea
>>>>
>>>>
>>>>>
>>>>> "GPL Ghostscript 9.25: Unrecoverable error, exit code 1" is not
>>>>> fatal and can be ignored as far as I know.
>>>>>
>>>>> Akira
>>>
>>
