Re: Errors when doing 'make' for the first time when building the fonts

2011-10-08 Thread Werner LEMBERG

 I've always these errors when I 'make' for the first time (i.e. when I
 have a fresh out of tree build).
 
 I expect most of them have always been there, but I wondered if they
 are problematic or not?

They are problematic, and they have not `always been there' :-)

Please use a recent version of FontForge, and please compile it with
`--enable-double'.

More details can be found in the archive of this email list.


Werner

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: Errors when doing 'make' for the first time when building the fonts

2011-10-08 Thread Peekay Ex
Werner

On Sat, Oct 8, 2011 at 7:05 AM, Werner LEMBERG w...@gnu.org wrote:

 I've always these errors when I 'make' for the first time (i.e. when I
 have a fresh out of tree build).

 I expect most of them have always been there, but I wondered if they
 are problematic or not?

 They are problematic, and they have not `always been there' :-)

 Please use a recent version of FontForge, and please compile it with
 `--enable-double'.

Can you tell me which command I add the --enable-double to?

'make -j7 --enable-double' or '../configure --enable-double' or something else?


 More details can be found in the archive of this email list.

yes I remember Trevor's email

Can you tell me though what the ramifications are in terms of reg test
checkig that I do if I am getting these errors?

Thanks again.

-- 
--
James

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: Errors when doing 'make' for the first time when building the fonts

2011-10-08 Thread David Kastrup
Werner LEMBERG w...@gnu.org writes:

 and the version string contains `-D' or `-LD', e.g.

  Executable based on sources from 23:14 GMT 25-Feb-2011-ML-TtfDb-D.
 ^^

 Unfortunately, Ubuntu Maverick (11.04) only ships a version from 2010:

 reinhold@eeepc:~$ fontforge --version
 Copyright (c) 2000-2010 by George Williams.
  Executable based on sources from 11:21 GMT 1-May-2010.

 At that time the additional configuration flags aren't shown in the
 version string of FontForge; this feature has been added later to the
 source code.  In other words, you have to look up Ubuntu's compilation
 script to find out whether they are using --enable-double or not.

The upcoming Oneiric (11.10) states

fontforge --version
Copyright (c) 2000-2011 by George Williams.
 Executable based on sources from 13:48 GMT 22-Feb-2011-ML.
 Library based on sources from 13:48 GMT 22-Feb-2011.
fontforge 20110222
libfontforge 20110222-ML

So you better file a problem report if you want this changed.  Not
likely for Oneiric, but you may be lucky for 12.04.

-- 
David Kastrup


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: Errors when doing 'make' for the first time when building the fonts

2011-10-08 Thread Graham Percival
On Sat, Oct 08, 2011 at 08:05:12AM +0200, Werner LEMBERG wrote:
 
  I expect most of them have always been there, but I wondered if they
  are problematic or not?
 
 They are problematic, and they have not `always been there' :-)

Correction: using our official development environment lilydev,
they *have* always been there.

 Please use a recent version of FontForge, and please compile it with
 `--enable-double'.

This warning is in the installation instructions, but it would be
nice if we didn't have warnings like that.  ../configure should
check it.  Fontforge  20110222 even shows the status of whether
you used --enable-double in the version string, so it would be an
easy check to make!
http://code.google.com/p/lilypond/issues/detail?id=1637

Unfortunately we cannot (in good faith) require this until it's in
lilydev.
http://code.google.com/p/lilypond/issues/detail?id=1683

Cheers,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: Errors when doing 'make' for the first time when building the fonts

2011-10-08 Thread Werner LEMBERG
 They are problematic, and they have not `always been there' :-)
 
 Correction: using our official development environment lilydev, they
 *have* always been there.

Hmm.

 Please use a recent version of FontForge, and please compile it
 with `--enable-double'.
 
 This warning is in the installation instructions, but it would be
 nice if we didn't have warnings like that.  ../configure should
 check it.  Fontforge  20110222 even shows the status of whether you
 used --enable-double in the version string, so it would be an easy
 check to make!

Yep.  If my memory serves right, someone has even written a patch for
that already.  No time to check the archives, sorry.


Werner

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Errors when doing 'make' for the first time when building the fonts

2011-10-07 Thread Peekay Ex
Hello,

I've always these errors when I 'make' for the first time (i.e. when I
have a fresh out of tree build).

I expect most of them have always been there, but I wondered if they
are problematic or not?

--snip--
Internal Error in accidentals.flat.arrowdown: monotonic is both needed
and unneeded.
Internal Error in accidentals.flat.arrowdown: monotonic is both needed
and unneeded.
Internal Error in accidentals.flat.arrowdown: Expected needed monotonic.
Internal Error in accidentals.flat.arrowboth: monotonic is both needed
and unneeded.
Internal Error in accidentals.flat.arrowboth: monotonic is both needed
and unneeded.
Internal Error in accidentals.flat.arrowboth: Expected needed monotonic.
Internal Error in accidentals.flat.arrowdown: monotonic is both needed
and unneeded.
Internal Error in accidentals.flat.arrowdown: monotonic is both needed
and unneeded.
Internal Error in accidentals.flat.arrowdown: Expected needed monotonic.
Internal Error in accidentals.flat.arrowboth: monotonic is both needed
and unneeded.
Internal Error in accidentals.flat.arrowboth: monotonic is both needed
and unneeded.
Internal Error in accidentals.flat.arrowboth: Expected needed monotonic.
@{char@:Flageolet@:115@:3.36@:3.36@:3.36@:3.36@:3.36@:0@:flageolet@}
[115]Internal Error in accidentals.flat.arrowdown:
Internal Error in accidentals.flat.arrowdown: monotonic is both needed
and unneeded.
Internal Error in accidentals.flat.arrowdown: Expected needed monotonic.
@} [151]Internal Error in clefs.G_change: monotonic is both needed and unneeded.
Internal Error in clefs.G_change: monotonic is both needed and unneeded.
Internal Error in clefs.G_change: monotonic is both needed and unneeded.
Internal Error in clefs.G_change: monotonic is both needed and unneeded.
Internal Error in clefs.G_change: monotonic is both needed and unneeded.
Internal Error in clefs.G_change: monotonic is both needed and unneeded.
Internal Error in clefs.G_change: monotonic is both needed and unneeded.
Internal Error in clefs.G_change: monotonic is both needed and unneeded.
Internal Error in clefs.G_change: monotonic is both needed and unneeded.
Internal Error in clefs.G_change: monotonic is both needed and unneeded.
Internal Error in clefs.G_change: monotonic is both needed and unneeded.
Internal Error in clefs.G_change: monotonic is both needed and unneeded.
Internal Error in clefs.G_change: Expected needed monotonic.
Internal Error in clefs.G_change: Expected needed monotonic.
Internal Error in clefs.G_change: Expected needed monotonic.
Internal Error in clefs.G_change: couldn't find a needed exit from an
intersection
Internal Error in clefs.G_change: Humph. This monotonic leads nowhere.
Internal Error in clefs.G_change: Expected needed monotonic.
Internal Error in clefs.G_change: Closing contour with unneeded path
Internal Error in clefs.G_change: Expected needed monotonic.
Internal Error in clefs.G_change: Expected needed monotonic.
Internal Error in clefs.G_change: Expected needed monotonic.
Internal Error in clefs.G_change: Expected needed monotonic.
Internal Error in clefs.G_change: Humph. This monotonic leads nowhere.
Internal Error in clefs.G_change: Expected needed monotonic.
Internal Error in clefs.G_change: Closing contour with unneeded path
Internal Error in clefs.G_change: Expected needed monotonic.
Internal Error in accidentals.sharp.arrowup: couldn't find a needed
exit from an intersection
Internal Error:
Internal Error in accidentals.sharp.arrowup: couldn't find a needed
exit from an intersection
Internal Error in accidentals.sharp.arrowboth: couldn't find a needed
exit from an intersection
Internal Error:
Internal Error in accidentals.sharp.arrowboth: couldn't find a needed
exit from an intersection
Internal Error in accidentals.flat.arrowboth: monotonic is both needed
and unneeded.
Internal Error in accidentals.flat.arrowboth: monotonic is both needed
and unneeded.
Internal Error in accidentals.flat.arrowboth: Expected needed monotonic.
Internal Error in accidentals.flat.arrowboth: monotonic is both needed
and unneeded.
Internal Error in accidentals.flat.arrowboth: monotonic is both needed
and unneeded.
Internal Error in accidentals.flat.arrowboth: Expected needed monotonic.
Internal Error in scripts.varcoda: couldn't find a needed exit from an
intersection
Internal Error:
Internal Error in scripts.varcoda: couldn't find a needed exit from an
intersection
--snip--



-- 
--
James

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel