> How do I correct the problem?
See David's answer – since I don't use Debian, I can't help with such
details.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
"Phil Holmes" writes:
>> dak@lola:/tmp$ dpkg -S
>> /usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/ecrm1095.mf
>> texlive-fonts-recommended:
>> /usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/ecrm1095.mf
>>
>> So my guess is that you need to install the texlive-fonts-recommended
>>
- Original Message -
From: "Werner LEMBERG"
To:
Cc: ;
Sent: Friday, February 27, 2015 7:20 PM
Subject: Re: GUB update
What about latt1095, which causes the next failure?
This is part of the Cyrillic LH fonts.
Werner
Thanks. How do I correct the problem?
--
P
> What about latt1095, which causes the next failure?
This is part of the Cyrillic LH fonts.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
- Original Message -
From: "David Kastrup"
To: "Phil Holmes"
Cc:
Sent: Friday, February 27, 2015 5:25 PM
Subject: Re: GUB update
Phil Holmes writes:
With huge thanks to Masamichi, I am within a whisker of getting GUB
working
again. I've built binarie
> kpathsea: Running mktexmf ecrm1095
texinfo uses some glyphs from the EC family, in particular
non-typewriter braces. A comment from texinfo.tex:
% @{ @} @lbracechar{} @rbracechar{} all generate brace characters.
% Unless we're in typewriter, use \ecfont because the CM text fonts do
%
Phil Holmes writes:
> With huge thanks to Masamichi, I am within a whisker of getting GUB working
> again. I've built binaries and regtest comparisons, but I'm just failing on
> the docs right now. The error is in trying to build collated-files. From
> lilypond-doc.log I get:
>
> Please check
With huge thanks to Masamichi, I am within a whisker of getting GUB working
again. I've built binaries and regtest comparisons, but I'm just failing on
the docs right now. The error is in trying to build collated-files. From
lilypond-doc.log I get:
Please check the logfile collated-files.texi2p
> The principle with GUB is that it has details of all the packages it uses,
> and by issuing the 'make bootstrap' command, it goes and gets all the
> packages it needs, and all their dependencies, and builds them all from
> scratch. The problem I believe I now have is that gcc 4.8 has a new
> dep
On Sun, Jan 04, 2015 at 04:33:05PM +, Phil Holmes wrote:
> I assume what is happening here is that the manual install places the mpc
> libraries where the gcc configur can't find them. In any case, doing this
> manually defeats the object of a self-building package builder. So what
> would be
A restatement of what is happening with GUB builds, and therefore an appeal
for help.
The current aim is to update gcc so it will compile more up to date template
syntax, and my target has been gcc 4.8.2. The previous version was 4.1.1.
I'm working with a new virtual machine running Ubuntu 14.04
Phil Holmes writes:
> Keen observers will have noticed that I've not been able to keep to my
> normal schedule of LilyPond releases. The is down to the fact that
> some of the recent patches are not compatible with the original GCC
> version in te GUB repo. I've been working on updating this, b
Keen observers will have noticed that I've not been able to keep to my
normal schedule of LilyPond releases. The is down to the fact that some
of the recent patches are not compatible with the original GCC version in
te GUB repo. I've been working on updating this, but having problems
getting
13 matches
Mail list logo
