-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Can anyone tell me why we have an entry
- -midly.ly
in .gitignore?
it seems to be coming back to bite me. It happened before when I
edited the MIDI section of the NR and had to create/edit some
snippets, and for whatever reason it seems to b
On Jun 17, 2015, at 17:43 , Kevin Barry wrote:
>
> make[1]: *** No rule to make target '../flower/./out/library.a', needed by
> 'out/lilypond'. Stop.
> make[1]: Leaving directory '/home/pi/src/lilypond-2.18.2/build/lily'
> /home/pi/src/lilypond-2.18.2/stepmake/stepmake/toplevel-targets.make:30:
Dear All,
During a transitional period where I have no computer I have tried
compiling the latest stable version of lilypond from source on a raspberry
pi to see if I could get it working. (The latest raspbian - still Debian
wheezy - is using 2.14.2 which will not work on most of my files.)
Everyt
Thanks.
Am 17.06.2015 um 16:13 schrieb David Kastrup:
Simon Albrecht writes:
Hello team,
in order for me to fulfill my new duty as a Bug Squad member, could
someone please add me as a contributor to the Issues database? (if
also it will be for two months only with google code :-)) I’m
regist
Simon Albrecht writes:
> Hello team,
>
> in order for me to fulfill my new duty as a Bug Squad member, could
> someone please add me as a contributor to the Issues database? (if
> also it will be for two months only with google code :-)) I’m
> registered there with this e-mail address, pseudonym
Hello team,
in order for me to fulfill my new duty as a Bug Squad member, could
someone please add me as a contributor to the Issues database? (if also
it will be for two months only with google code :-)) I’m registered
there with this e-mail address, pseudonym ‘Ton Mahler’.
Thanks,
Simon
_
Il giorno mer 17 giu 2015 alle 9:50, Trevor Daniels
ha scritto:
I take the point about not being greedy, but I wonder if we want to
retain an option to compile Allura from source. Clearly we don't
want to get into Allura development, but there are already many
patches applied to the source th
Am 17.06.2015 um 10:19 schrieb Werner LEMBERG:
>
>> I take the point about not being greedy, but I wonder if we want to
>> retain an option to compile Allura from source.
>
> This is even the preferred installation way, right? However, 1GB of
> RAM should be fully sufficient for compilation, I
> I take the point about not being greedy, but I wonder if we want to
> retain an option to compile Allura from source.
This is even the preferred installation way, right? However, 1GB of
RAM should be fully sufficient for compilation, I reckon.
Werner
> We are only going to run Allura here right now, no compilers and
> other stuff.
Agreed, but...
> We don't want to get as low in memory as to significantly increase
> disk traffic.
... I'm worried by the necessary amount of RAM for the database
front-end.
> But since we are not going to run a
David Kastrup wrote Wednesday, June 17, 2015 8:33 AM
> Everybody wants as much as possible and the point of a VM is to support
> multiple tasks. So it would be good if we could narrow it down
> somewhat. We are only going to run Allura here right now, no compilers
> and other stuff. We don't w
Werner LEMBERG writes:
>>> I've checked the two processes running (see attachment). Of course
>>> I'm not _using_ allura, it's open in my browser but I'm not doing
>>> anything. I don't know if this is useful at all... Maybe we'd
>>> better ask the Allura people..
>>
>> Why don't we just see wh
12 matches
Mail list logo
