[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Ghostscript problem in 2.19.18
From: |
Masamichi HOSODA |
Subject: |
Re: Ghostscript problem in 2.19.18 |
Date: |
Mon, 13 Apr 2015 21:19:33 +0900 (JST) |
> This is on Debian with the linux-386 binary and applies to _any_ file,
> even
> { c }
> .
>
> Compiling with the 2.19.17 binary works.
> Compiling with the 2.19.18 binary fails.
> Compiling with a custom build from current master works.
>
> As there are no relevant commits between the 2.19.18 tag and current
> master I assume this is due to the binary build (i.e. recent GUB
> changes).
I've tested official binary lilypond-2.19.18-1.linux-x86.sh
on both Ubuntu 32 bit and Ubuntu 64 bit.
It is fine for my both environments.
- Ghostscript problem in 2.19.18, Urs Liska, 2015/04/13
- Re: Ghostscript problem in 2.19.18, Federico Bruni, 2015/04/13
- Re: Ghostscript problem in 2.19.18,
Masamichi HOSODA <=
- Re: Ghostscript problem in 2.19.18, Urs Liska, 2015/04/13
- Re: Ghostscript problem in 2.19.18, Masamichi HOSODA, 2015/04/13
- Re: Ghostscript problem in 2.19.18, Urs Liska, 2015/04/13
- Re: Ghostscript problem in 2.19.18, Masamichi HOSODA, 2015/04/13
- Re: Ghostscript problem in 2.19.18, Urs Liska, 2015/04/13
- Re: Ghostscript problem in 2.19.18, Masamichi HOSODA, 2015/04/14
- Re: Ghostscript problem in 2.19.18, Urs Liska, 2015/04/14
- Re: Ghostscript problem in 2.19.18, Masamichi HOSODA, 2015/04/15