lilypond-devel
[Top][All Lists]
Advanced

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

Re: GUB lilypond build fails


From: David Kastrup
Subject: Re: GUB lilypond build fails
Date: Sun, 30 Dec 2018 20:07:44 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)

"Phil Holmes" <address@hidden> writes:

> ----- Original Message ----- 
> From: "David Kastrup" <address@hidden>
> To: "Phil Holmes" <address@hidden>
> Cc: "Werner LEMBERG" <address@hidden>; <address@hidden>
> Sent: Sunday, December 30, 2018 6:46 PM
> Subject: Re: GUB lilypond build fails
>
>
>> "Phil Holmes" <address@hidden> writes:
>>
>>> ----- Original Message ----- 
>>> From: "Phil Holmes" <address@hidden>
>>> To: "Werner LEMBERG" <address@hidden>
>>> Cc: <address@hidden>; <address@hidden>
>>> Sent: Sunday, December 30, 2018 12:29 PM
>>> Subject: Re: GUB lilypond build fails
>>>
>>>
>>>>
>>>> The problem with "NewGub" would seem to be my issue.  I've always
>>>> made and uploaded GUB in a VM with a user gub and a directory called
>>>> NewGub under that user's home directory.  I'm currently trying to
>>>> build from a user with a home directory called gubd and in a
>>>> directory called GubDir.  I do have a user called gub (it's where
>>>> the VM lives) and could create a directory called NewGub and try to
>>>> see if this works at this time.  Watch this space.
>>>
>>>
>>> Success building from master. Thanks Werner.  Will take me a time to
>>> sort out a build from the stable candidate, but it looks like we're on
>>> track.
>>>
>>> make lilypond took 4 hours on a core i7 with 4 core, 8 hyperthreads...
>>
>> That does not say a lot without specifying the generation.  I have in my
>> laptop a
>>
>> model name : Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz
>
>
> core i7-2600 3.4GHz.  About 8 years old....

Oh, 2nd generation like mine.  It's not a mobile, but the difference in
speed should actually be sort-of proportional to the clock frequency.

-- 
David Kastrup



reply via email to

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