lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fwd: Compiling on Mac OS X


From: Patrick McCarty
Subject: Re: Fwd: Compiling on Mac OS X
Date: Sat, 27 Dec 2008 14:42:15 -0800
User-agent: Mutt/1.5.18 (2008-05-17)

On Sat, Dec 27, 2008 at 10:56:18PM +0100, Arjan Bos wrote:
>
> On 27 dec 2008, at 21:07, August Lilleaas wrote:
>
>> I were doing this on HEAD. Changed to 2.10.9-1, and (for some reason) 
>> doing make, then make all (both yielding errors) and then make worked.
>>
>> After running a couple of minutes, though, this happened:
>>
>> out/lexer.cc:384: error: no 'int yyFlexLexer::yywrap()' member  
>> function declared in class 'yyFlexLexer'
>>
>> Am I the only person that wants to run lilypond on a modern intel mac, 
>> or have I overlooked something?
>
> I'm having the same problem. What I did to solve this is removing the  
> line containing yywrap in FlexLexer.h. If you've been following Nicolas' 
> guidelines, then that file is:
> /opt/local/include/FlexLexer.h
> and the line-number is arround 130
>
> I tried this with HEAD  and I get the following:
> Processing `/usr/local/src/lilypond/lilypond/ly/generate- 
> documentation.ly'
> Parsing...[/usr/local/src/lilypond/lilypond/out/share/lilypond/current/ 
> ly/init.lyAssertion failed: (pt->read_pos == pt->read_end), function  
> scm_fill_input, file ports.c, line 978.
> /bin/sh: line 1: 21318 Abort trap              /usr/local/src/lilypond/ 
> lilypond/out/bin/lilypond --verbose /usr/local/src/lilypond/lilypond/ 
> ly/generate-documentation
>
> And now I'm at a loss, because I don't have a ports.c file on my  
> computer (according to locate)
>
> Can someone chime in here please? Or should I take my quest for Intel  
> Mac OS X Lilypond to a developer list?

The file ports.c is part of the Guile source code.  I have experienced
this error on GNU/Linux with Guile 1.8.6, and it appears to be a known
issue:

http://lists.gnu.org/archive/html/guile-devel/2008-12/msg00043.html

I will post a report to the bug-lilypond list soon.

-Patrick




reply via email to

[Prev in Thread] Current Thread [Next in Thread]