Re: How to end a melisma

2017-11-02 Thread David Wright 
On Thu 02 Nov 2017 at 09:59:38 (-0400), Ben wrote:
> On 11/2/2017 9:07 AM, Patrick Karl wrote:

> >It may be the correct way, but the drawback seems to be that it
> >doesn't work.  At least on my Mac running OSX 10.11.6 and LilyPond
> >v 2.19.53.

> I am confused, if you just wanted it to end earlier couldn't you
> just alter the lyrics code?
> Or did you want just blank space there and not move the 'sol la
> ti...' to the left?
> Sorry, I don't quite understand.

I print a lot of "SATB" music (actually Ten/Lead/Bari/Bass) which
is predominantly on two staves with lyrics in between. However,
there are obviously passages where one or more parts sing different
lyrics or rhythms from the "main thread" for which I write sparse
lyrics above or below the system; sometimes even two lines of lyrics
between the staves. So lines of sparse lyrics are the norm—no one
wants four lines of lyrics wherever the parts are all in step.

I don't like using _ _ _ _ because they confuse the eye en masse,
so   \repeat unfold 99 _   is my preferred construction; in this
case for 100 skipped syllables. For the melisma "stopper", I use
\n for the simple reason that it stands out in a listing, and
the syntax highlighter in my editor colours it differently from
normal lyrics (including ""). Of course, that means I have
n = \lyricmode { "" }   defined in my standard .ily file.

So the OP's example might look like

Lyrics = \lyricmode {
  do re mi fa __ _ _ _ _ \n
  \repeat unfold 2 _
  sol la ti do
}

\repeat unfold 2 _   might look stupid, but
\repeat unfold 132 _   less so. Putting it on a separate line
makes it easier to duplicate in most editors, so that you
don't have to type it over and over.

Cheers,
David.

PS Ben, I'm curious as to whether you have a long commute across
two or three time zones? (Hope you don't mind me asking.)

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fixing Lead Sheet Chord Numbers

2017-11-02 Thread Flaming Hakama by Elaine 
> From: Reilly Farrell 
> To: lilypond-user 



> Hi All,
>
> I'm discovering the need to revise chord numbers when working with lead
> sheet templates in LilyPond.  For example, in the following blocks:
>
> melody = \relative c' {
> cis8 d e g a4-. g8-> b~-_ |
> }
>
> chordSymbols = \chords { \leadFormatting
> a2:7 c2:13
> }
>
> ...my intention is to have c2:13 show up as C13.  Instead, the output is
> C9 13, and I'm not sure how to take more explicit control and remove the
> 9.  Any suggestions are deeply appreciated.  Thank you!
>
>

The way to customize chord symbols is covered in
http://lilypond.org/doc/v2.19/Documentation/notation/displaying-chords#customizing-chord-names

Under the heading "Selected Snippets, Chord name exceptions"


Here is how to get the Dominant 13th chord to show up as "13".


\version "2.19.15"

myChordExceptions = {
  1-\markup { \raise #0.7 { \normalsize 13 } }
}
chExceptions = #(append (sequential-music-to-chord-exceptions
myChordExceptions #t) ignatzekExceptions)

chordSequence = \chordmode {
\set chordChanges = ##t
\set chordNameExceptions = #chExceptions
a2:7
c2:13
}

myMelody = \relative c' { cis8 d e g a4-. g8-> b~-_ }

\score {
  \new StaffGroup <<
\new ChordNames \chordSequence
\new Staff {
  \myMelody
}
  >>
}


HTH,

David Elaine Alt
415 . 341 .4954   "*Confusion is
highly underrated*"
ela...@flaminghakama.com
self-immolation.info
skype: flaming_hakama
Producer ~ Composer ~ Instrumentalist
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to get the hairpin to the barline?

2017-11-02 Thread Noeck 
… or you tell lilypond to end the hairpin after the note by writing:
  4. <>\!
instead of
  4.\!
So you end it on an empty chord (which takes no time).


\score {
\relative c'' {
  \mergeDifferentlyHeadedOn \mergeDifferentlyDottedOn
   \override Hairpin.to-barline = ##t
<<  {
  \voiceOne
   a,8 
   _( )^\> 4. <>\! |
   } \\ {
   \voiceTwo
   a,2. a8( b) |
   } >>
}}

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to get the hairpin to the barline?

2017-11-02 Thread Ben 

On 11/2/2017 7:50 PM, Pieter Terpstra wrote:

Dear people,
Have looked this up in the lilypond doc and it work in the example there but no 
in mine, which is a bit different.

How do i do this?

Example:
\version "2.18.2"

\score {
\relative c'' {
   \mergeDifferentlyHeadedOn \mergeDifferentlyDottedOn
\override Hairpin.to-barline = ##t
<<  {
   \voiceOne
a,8 _()^\>4.\! |
} \\ {
\voiceTwo
a,2. a8 (b) |
} >>
}}

Thank you so much in advance!

Peter



Hi Peter,

I have not used v2.18 in quite some time, but I believe you could do 
something like this...and adjust to taste.

(see attached)

Does this help?

\version "2.18.2"

\score {
\relative c'' {
  \mergeDifferentlyHeadedOn \mergeDifferentlyDottedOn
   \override Hairpin.to-barline = ##t
<<  {
  \voiceOne
   a,8 
*  \override Hairpin.shorten-pair = #'(0 . -5)*
   _()^\>4.\! |
   } \\ {
   \voiceTwo
   a,2. a8 (b) |
   } >>
}}


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

How to get the hairpin to the barline?

2017-11-02 Thread Pieter Terpstra 
Dear people,
Have looked this up in the lilypond doc and it work in the example there but no 
in mine, which is a bit different.

How do i do this?

Example:
\version "2.18.2"

\score {
\relative c'' {
  \mergeDifferentlyHeadedOn \mergeDifferentlyDottedOn
   \override Hairpin.to-barline = ##t
<<  { 
  \voiceOne
   a,8 _()^\>4.\! |
   } \\ {
   \voiceTwo
   a,2. a8 (b) | 
   } >>  
}}

Thank you so much in advance!

Peter


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to end a melisma

2017-11-02 Thread Simon Albrecht 

On 02.11.2017 14:07, Patrick Karl wrote:

On 10/31/17 7:19 PM, Simon Albrecht wrote:

On 31.10.2017 18:09, pkarl wrote:
I'm trying to figure out the correct way to have LilyPond, v2.19.53, 
generate the attached score, which is for an instrument and a 
singer, but the singer doesn't sing all the notes that the 
instrumentalist plays. Furthermore, the last thing before the singer 
tacet's is a melisma.


My first naive attempt was:

Music = \relative c'' { c4 d e f    c d e f    r d e f    c d e f }
Lyrics = \lyricmode { do re mi fa __ _ _ _ _
\repeat unfold 3 { \skip 1 } sol la ti do }
\score {
    \new Staff \Music
    \addlyrics \Lyrics
} 


The correct way would be

Music = \relative c'' {
  c4 d e f\melisma
  c d e f\melismaEnd
  r d e f
  c d e f
}
Lyrics = \lyricmode {
  do re mi fa __
  _ _ _
  sol la ti do
}
\score {
  \new Staff \Music
  \addlyrics \Lyrics
}

Best, Simon 


It may be the correct way, but the drawback seems to be that it 
doesn't work.  At least on my Mac running OSX 10.11.6 and LilyPond v 
2.19.53.


I ran your suggested solution, named SimonAlbrechtsSolution.ly, via 
Frescobaldi.  I am attaching the LilyPond file, the output pdf, and a 
screenshot of the LilyPond log file.  You will note in the pdf that 
the melisma extender does not stop at the end of measure 2 but 
continues right through measure 3.  I need it to stop at the end of 
measure 2.


May I ask what version of LilyPond you ran your solution on?



I’m sorry, the problem is that I overconfidently answered without 
actually trying the code and without remembering that _ doesn’t 
terminate a melisma. So you have to combine my solution and Malte’s by 
replacing the first single underscore in my example by "".


Best, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fixing Lead Sheet Chord Numbers

2017-11-02 Thread Ben 

On 11/2/2017 2:45 PM, Reilly Farrell wrote:
Thank you for your reply!  I should have started by mentioning I'm 
working in Version 2.18.2.  I've tinkered with the sample code a bit 
more - the following block should serve our purposes better:


\version "2.18.2"

\score {
<<
\relative c' {
c4 c c c |
}

\chords {
c4:13 c4:11 c4:13.11+ c4:aug7
}
>>
\layout{}
\midi{}
}

The intent here is to find a way to print the first, third and fourth 
chords without 9 and 7.




Hi Reilly,

Here is some code to help you with the chords.
Let us know if you need more than this...
(see attached)

PS. Don't forget to hit reply all or reply to list when responding to 
messages :) That way everyone gets them, not just who you're replying to.


%%

\version "2.18.2"

\score {
<<
\relative c' {
c4 c c c |
}

\chords {
*c4:13.11 **
**c4:11 **
**c4:5.13.11+ **
**c4:aug*
}
>>
\layout{}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Adding Space Between Tempo Mark And First System

2017-11-02 Thread Ben 

On 11/2/2017 12:13 PM, Reilly Farrell wrote:

Hi All,

I'm searching for a way to add extra space between the tempo 
indication and the first system of music, to make room for markup 
content above the staff.  (The default space allotted to the markup 
content right now is not sufficient and the score looks a bit 
cluttered.)  Is there a simple way of accomplishing this?



I believe this code is what you are looking for:

\version "2.19.80"

{
*\override Score.MetronomeMark.padding = #3*
  \tempo "Very fast" c d e f }

Make sure to tell us what version of LilyPond you are using, because 
sometimes syntax changes make a difference...



(see attached)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fixing Lead Sheet Chord Numbers

2017-11-02 Thread Ben 

On 11/2/2017 12:01 PM, Reilly Farrell wrote:

Hi All,

I'm discovering the need to revise chord numbers when working with 
lead sheet templates in LilyPond.  For example, in the following blocks:


melody = \relative c' {
cis8 d e g a4-. g8-> b~-_ |
}

chordSymbols = \chords { \leadFormatting
a2:7 c2:13
}

...my intention is to have c2:13 show up as C13.  Instead, the output 
is C9 13, and I'm not sure how to take more explicit control and 
remove the 9.  Any suggestions are deeply appreciated.  Thank you!




Hi Reilly,

Could you supply us with some more info?
What version are you using, and also a minimal example that we can 
compile to see your output?


It would help us be able to help you :)

*melody = \relative c' {**
**cis8 d e g a4-. g8-> b~-_ |**
**}**
**
**chordSymbols = \chords { \leadFormatting**
**a2:7 c2:13 **
**}*

...does not compile because obviously we don't have enough to work with 
- yet.


Thanks!
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Adding Space Between Tempo Mark And First System

2017-11-02 Thread Reilly Farrell 
Hi All,

I'm searching for a way to add extra space between the tempo indication and
the first system of music, to make room for markup content above the
staff.  (The default space allotted to the markup content right now is not
sufficient and the score looks a bit cluttered.)  Is there a simple way of
accomplishing this?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Fixing Lead Sheet Chord Numbers

2017-11-02 Thread Reilly Farrell 
Hi All,

I'm discovering the need to revise chord numbers when working with lead
sheet templates in LilyPond.  For example, in the following blocks:

melody = \relative c' {
cis8 d e g a4-. g8-> b~-_ |
}

chordSymbols = \chords { \leadFormatting
a2:7 c2:13
}

...my intention is to have c2:13 show up as C13.  Instead, the output is C9
13, and I'm not sure how to take more explicit control and remove the 9.
Any suggestions are deeply appreciated.  Thank you!
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spanner and epsfile

2017-11-02 Thread David Nalesnik 
Harm,

On Wed, Nov 1, 2017 at 5:22 PM, Thomas Morley  wrote:
> 2017-11-01 23:11 GMT+01:00 David Nalesnik :
>> On Wed, Nov 1, 2017 at 2:27 PM, Thomas Morley  
>> wrote:
>>> 2017-11-01 4:21 GMT+01:00 Bernardo Barros :
>>>
 I'm still trying to figure out my other question, how to have
 inter-penetrating spanners, or rather, how to have one spanner parallel to
 another without conflict?

 I can imagine two solutions:

 1) Two or more voices, one with all notes hidden. Ugly solution.
>>>
>>> There's only one TextSpanner per Voice possible, so above is certainly
>>> a possibility
>>
>> Attached to the following is some code which will allow you to have
>> multiple TextSpanners per voice.  I haven't tried to apply it to your
>> use case, though.
>>
>> http://lists.gnu.org/archive/html/lilypond-user/2015-10/msg00551.html
>
> Hi David,
>
> nice one and cheaper than my own (no grob-creation).
> I must have missed it back in 2015.
>
> Would be nice to have it in the .cc-file.
> Any chance?

I could add it, yes.  My concern is that work was been done to make
'spanner-id work generally with spanners -- David Kastrup?  But if
that's a distant possibility, I would be happy to work it into a .cc
patch.

-David

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to end a melisma

2017-11-02 Thread Ben 

On 11/2/2017 9:07 AM, Patrick Karl wrote:


It may be the correct way, but the drawback seems to be that it 
doesn't work.  At least on my Mac running OSX 10.11.6 and LilyPond v 
2.19.53.



I ran your suggested solution, named SimonAlbrechtsSolution.ly, via 
Frescobaldi.  I am attaching the LilyPond file, the output pdf, and a 
screenshot of the LilyPond log file.  You will note in the pdf that 
the melisma extender does not stop at the end of measure 2 but 
continues right through measure 3.  I need it to stop at the end of 
measure 2.



May I ask what version of LilyPond you ran your solution on?




I am confused, if you just wanted it to end earlier couldn't you just 
alter the lyrics code?
Or did you want just blank space there and not move the 'sol la ti...' 
to the left?

Sorry, I don't quite understand.

(see attached)

Music = \relative c'' {
  c4^\markup { "" } d e f\melisma
  c d e f\melismaEnd
  r d e f
  c d e f
}
Lyrics = \lyricmode {
  do re mi fa __

  sol la ti do
}
\score {
  \new Staff \Music
  \addlyrics \Lyrics
}



instead of

Lyrics = \lyricmode {
  do re mi fa __
*  _ _ _*
  sol la ti do
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spanner and epsfile

2017-11-02 Thread David Nalesnik 
On Wed, Nov 1, 2017 at 6:28 PM, Thomas Morley  wrote:
> 2017-11-01 23:30 GMT+01:00 Bernardo Barros :
>> On 11/1/17 18:11, David Nalesnik wrote:
>>>
>>> Attached to the following is some code which will allow you to have
>>> multiple TextSpanners per voice.  I haven't tried to apply it to your
>>> use case, though.
>>>
>>> http://lists.gnu.org/archive/html/lilypond-user/2015-10/msg00551.html
>>
>>
>> I see only one Spanner in the output [see image]
>>
>>
>
> There was a change in type-predicate for spanner-id. It's now 'key?'.
>

Thank you for the fix, Harm!

David

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to end a melisma

2017-11-02 Thread Patrick Karl 

On 10/31/17 7:19 PM, Simon Albrecht wrote:

On 31.10.2017 18:09, pkarl wrote:
I'm trying to figure out the correct way to have LilyPond, v2.19.53, 
generate the attached score, which is for an instrument and a singer, 
but the singer doesn't sing all the notes that the instrumentalist 
plays. Furthermore, the last thing before the singer tacet's is a 
melisma.


My first naive attempt was:

Music = \relative c'' { c4 d e f    c d e f    r d e f    c d e f }
Lyrics = \lyricmode { do re mi fa __ _ _ _ _
\repeat unfold 3 { \skip 1 } sol la ti do }
\score {
    \new Staff \Music
    \addlyrics \Lyrics
} 


The correct way would be

Music = \relative c'' {
  c4 d e f\melisma
  c d e f\melismaEnd
  r d e f
  c d e f
}
Lyrics = \lyricmode {
  do re mi fa __
  _ _ _
  sol la ti do
}
\score {
  \new Staff \Music
  \addlyrics \Lyrics
}

Best, Simon 


It may be the correct way, but the drawback seems to be that it doesn't 
work.  At least on my Mac running OSX 10.11.6 and LilyPond v 2.19.53.



I ran your suggested solution, named SimonAlbrechtsSolution.ly, via 
Frescobaldi.  I am attaching the LilyPond file, the output pdf, and a 
screenshot of the LilyPond log file.  You will note in the pdf that the 
melisma extender does not stop at the end of measure 2 but continues 
right through measure 3.  I need it to stop at the end of measure 2.



May I ask what version of LilyPond you ran your solution on?

\version "2.19.53"

%{
On 31.10.2017 18:09, pkarl wrote:
> I'm trying to figure out the correct way to have LilyPond, v2.19.53, generate 
> the attached score, which is for an instrument and a singer, but the singer 
> doesn't sing all the notes that the instrumentalist plays. Furthermore, the 
> last thing before the singer tacet's is a melisma.
>
> My first naive attempt was:
>
> Music = \relative c'' { c4 d e fc d e fr d e fc d e f }
> Lyrics = \lyricmode { do re mi fa __ _ _ _ _
> \repeat unfold 3 { \skip 1 } sol la ti do }
> \score {
> \new Staff \Music
> \addlyrics \Lyrics
> } 

The correct way would be
%}

Music = \relative c'' {
  c4^\markup { "Simon Albrecht's solution" } d e f\melisma
  c d e f\melismaEnd
  r d e f
  c d e f
}
Lyrics = \lyricmode {
  do re mi fa __
  _ _ _
  sol la ti do
}
\score {
  \new Staff \Music
  \addlyrics \Lyrics
}

%{
Best, Simon 
%}

SimonAlbrechtsSolution.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond-2.19.80-1.linux-64.sh

2017-11-02 Thread David Kastrup 
Blöchl Bernhard  writes:

> May be I have not correctly explained the problem.

Maybe you refuse to understand the problem in spite of it getting
explained again and again.

> First, I HAVE installed a 64bit version of Linux
> Aspire-ES1-571 ~ $ uname -a
> Linux bb-Aspire-ES1-571 4.10.0-38-generic #42~16.04.1-Ubuntu SMP Tue
> Oct 10 16:30:51 UTC 2017 i686 i686 i686 GNU/Linux

No, this is a 32bit version of Linux.  A 64bit version would be x86_64
rather than i686.

> Second, as a fact I CANNOT get installed the 64bit version of lilypond
> on that system!

Because it is a 32bit system.

> I only could install the 32bit version and I did. At least I have a
> running version of lilypond.
>
> But I wanted to make that curiousity public. Do have other users that
> experience?

Unless you are going to install a 64bit system, you are not going to be
able to run a 64bit version of LilyPond.  Or a 64bit version of _any_
software.

I am leaving the rest of the (increasingly incredible) conversation
appended for reference.

> Am 01.11.2017 09:44, schrieb  bit version of Linux
> David Kastrup:
>> Blöchl Bernhard  writes:
>>
>>> The 32 bit lilypond installs without problem. No further problem.
>>>
>>> I find it curious that a 64 bit linux installs seamlessly on that
>>> laptop.
>>
>> Why wouldn't it?  Most modern CPUs support 64 bit mode.
>>
>>> Linux Mint definitely does not install a 64 bit version on a 32 bit
>>> systems but definitely cries for a 32 bit install.
>>
>> Your laptop is perfectly fine with 64 bit systems.  But you installed a
>> 32 bit system.  Which the laptop is fine with also.  But current CPUs
>> tend to be optimized for performance in 64 bit mode, so unless your
>> physical memory and disk space make it prudent to stick with 32 bits
>> (like having less than 4GB of main memory or your disk almost filled
>> up), upgrading to 64 bit systems makes sense.
>>
>>> Concerning to reports about Pentium 3556U
>>> it offers 64-bit OS support, Features SSE3 / SSE4.1 / SSE4.2
>>> instructions
>>> May be "OS support" is something less then full 64 bit support? (May
>>> be a possible explanation.)
>>
>> Your CPU would support 64 bit systems, but you are not running a 64 bit
>> system.
>>
>> A 32 bit kernel _cannot_ run 64 bit code, even if the CPU itself would
>> be capable of it.
>>
>> In contrast, a 64 bit kernel can be made to run 32 bit applications as
>> well.  Within limits: some ioctl calls are inherently system dependent,
>> so running 32bit sound applications (for example) on a 64 bit kernel is
>> likely to cause trouble.
>>
>>> Eventually there is a compiler option missing in make? I do not do
>>> further analyses.
>>
>> Make has nothing to do with it.
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond-2.19.80-1.linux-64.sh

2017-11-02 Thread Blöchl Bernhard 

May be I have not correctly explained the problem.

First, I HAVE installed a 64bit version of Linux
Aspire-ES1-571 ~ $ uname -a
Linux bb-Aspire-ES1-571 4.10.0-38-generic #42~16.04.1-Ubuntu SMP Tue Oct 
10 16:30:51 UTC 2017 i686 i686 i686 GNU/Linux


Second, as a fact I CANNOT get installed the 64bit version of lilypond 
on that system! I only could install the 32bit version and I did. At 
least I have a running version of lilypond.


But I wanted to make that curiousity public. Do have other users that 
experience?


Regards BB


Am 01.11.2017 09:44, schrieb  bit version of Linux
David Kastrup:

Blöchl Bernhard  writes:


The 32 bit lilypond installs without problem. No further problem.

I find it curious that a 64 bit linux installs seamlessly on that
laptop.


Why wouldn't it?  Most modern CPUs support 64 bit mode.


Linux Mint definitely does not install a 64 bit version on a 32 bit
systems but definitely cries for a 32 bit install.


Your laptop is perfectly fine with 64 bit systems.  But you installed a
32 bit system.  Which the laptop is fine with also.  But current CPUs
tend to be optimized for performance in 64 bit mode, so unless your
physical memory and disk space make it prudent to stick with 32 bits
(like having less than 4GB of main memory or your disk almost filled
up), upgrading to 64 bit systems makes sense.


Concerning to reports about Pentium 3556U
it offers 64-bit OS support, Features SSE3 / SSE4.1 / SSE4.2
instructions
May be "OS support" is something less then full 64 bit support? (May
be a possible explanation.)


Your CPU would support 64 bit systems, but you are not running a 64 bit
system.

A 32 bit kernel _cannot_ run 64 bit code, even if the CPU itself would
be capable of it.

In contrast, a 64 bit kernel can be made to run 32 bit applications as
well.  Within limits: some ioctl calls are inherently system dependent,
so running 32bit sound applications (for example) on a 64 bit kernel is
likely to cause trouble.


Eventually there is a compiler option missing in make? I do not do
further analyses.


Make has nothing to do with it.


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user