Hi Ian,
Ian Hulin skribis:
> (for-each ly:load init-scheme-files)
>
> Most of these files assume definitions are going into the default (lily)
> module, but some .scm files lower down the list reference definitions
> declared in a .scm file above it in the list.
>
> My question is this:
>
Hi Cédric,
ri...@happyleptic.org skribis:
> Ok, the problem is straightforward: fport_input_waiting is using select
> with a predefined SELECT_SET_SIZE of 1024. Although guile does not see
> the many files used by the applications, it may ends up with a file
> descriptor whose number is bigger th
Hi,
I'm currently working on getting Lilypond to use Guile V2 and compiled
Scheme files.
Currently, using V1.8.7, the Lilypond image fires up a lily.scm file
which includes as list of other .scm files. The initialization code in
the program declares a (lily) module and adjusts %load-path enable
Ok, the problem is straightforward: fport_input_waiting is using select
with a predefined SELECT_SET_SIZE of 1024. Although guile does not see
the many files used by the applications, it may ends up with a file
descriptor whose number is bigger than that. Then the select will
block forever.
Increa
