On 3/28/10 5:47 PM, "Patrick McCarty" wrote:
>
> I'm still in foreign territory here, but I have a possible solution
> for your problem. Can you test the attached patch instead of the one
> I send to you earlier?
>
> I just posted a patch to Rietveld as well:
> http://codereview.appspot.com/8
On Sun, Mar 28, 2010 at 10:12 AM, Patrick McCarty wrote:
> On 2010-03-28, Carl Sorensen wrote:
>>
>> Perhaps we have different versions of gcc. I'm using the following:
>>
>> sorensen2:~ Carl$ gcc --version
>> i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5493)
>
> Yes, we do have di
On 2010-03-28, Carl Sorensen wrote:
>
> On 3/27/10 11:56 PM, "Patrick McCarty" wrote:
>
> > On Sat, Mar 27, 2010 at 6:53 PM, Carl Sorensen wrote:
> >
> >> open-type-font.cc: In member function 'virtual size_t
> >> Open_type_font::index_to_charcode(size_t) const':
> >> open-type-font.cc:244: er
On Sat, Mar 27, 2010 at 6:53 PM, Carl Sorensen wrote:
>
> I'm working on OSX 10.5.8.
>
> I've downloaded the new repository.
>
> I've gone through the standard setup I've been using to build LilyPond.
>
> When I do make, I get the following:
[snip]
> open-type-font.cc: In member function 'virtua
Hi,
I'm working on OSX 10.5.8.
I've downloaded the new repository.
I've gone through the standard setup I've been using to build LilyPond.
When I do make, I get the following:
rm -f ./out/open-type-font-scheme.dep;
DEPENDENCIES_OUTPUT="./out/open-type-font-scheme.dep
./out/open-type-font-schem
hi,
with latest CVS,
make clean; make
complains that it doesn't know how to build mf/out/fonts.cache-1.
--
Erik
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Oops, this particular error was not related to -DSTRING_UTILS_NEEDED, it
occurs using default settings of ./configure as well.
Erik
On Sunday 08 May 2005 20.39, Erik Sandberg wrote:
> Hi,
>
> Make seems to fail when -DSTRING_UTILS_INLINED isn't passed to gcc (e.g.
> when --no-optimising is passe
Hi,
Make seems to fail when -DSTRING_UTILS_INLINED isn't passed to gcc (e.g. when
--no-optimising is passed to configure). The place of the first occurance of
the problem seems to vary randomly between minor lily versions, but this is
the last lines from 'configure --disable-optimising && make'
