headers
Graham Percival | 1 Jun 2009 07:49
Picon
Favicon

Re: GUB on kainhofer: still cross/gcc

On Sun, May 31, 2009 at 09:20:24PM +0200, Jan Nieuwenhuizen wrote:
> Op zaterdag 30-05-2009 om 22:46 uur [tijdzone -0700], schreef Graham
> Percival:
> 
> > Who has successfully built GUB?
> 
> Me!  :-)

Anybody else?  Particularly on ubuntu systems?

> >     def compile_command (self):
> >         os.putenv('CFLAGS', '-fno-stack-protector ')
> >         return (cross.AutoBuild.compile_command (self))
> > to the class Gcc (cross.AutoBuild), but that also failed.
> 
> FWIW, I'd very much avoid juggling with the environment from python,
> and try to keep changes as local as you can.

None of the other places I put -fno-stack-protector had any
effect, so I was just trying everything.  :(

> I'd try something like
> 
> diff --git a/gub/specs/darwin/odcctools.py b/gub/specs/darwin/odcctools.py
> index ee953c0..1d24944 100644
> --- a/gub/specs/darwin/odcctools.py
> +++ b/gub/specs/darwin/odcctools.py
>  <at>  <at>  -62,3 +62,8  <at>  <at>  cd %(install_prefix)s%(cross_dir)s/bin && ln %(toolchain_prefix)sstrip ../%(targ
>      def install (self):
>          cross.AutoBuild.install (self)
(Continue reading)

Permalink | Reply | 8 comments |
headers
Graham Percival | 1 Jun 2009 09:15
Picon
Favicon

Re: GUB on kainhofer: still cross/gcc

On Sun, May 31, 2009 at 09:20:24PM +0200, Jan Nieuwenhuizen wrote:
> diff --git a/gub/specs/darwin/odcctools.py b/gub/specs/darwin/odcctools.py
> index ee953c0..1d24944 100644
> --- a/gub/specs/darwin/odcctools.py
> +++ b/gub/specs/darwin/odcctools.py
>  <at>  <at>  -62,3 +62,8  <at>  <at>  cd %(install_prefix)s%(cross_dir)s/bin && ln %(toolchain_prefix)sstrip ../%(targ
>      def install (self):
>          cross.AutoBuild.install (self)
>          self.install_librestrict_stat_helpers ()
> +
> +class Odcctools__darwin__ppc (Odcctools):
> +    def configure_command (self):
> +        return (Odcctools.configure_command (self)
> +                + ' CFLAGS=-fno-stack-protector')

Update: according to
  https://wiki.ubuntu.com/CompilerFlags
the "*** buffer overflow detected" message comes from
-D_FORTIFY_SOURCE, not -fstack-protector.  I'm trying it now with
this option disabled; I'll report back in a few hours.

Cheers,
- Graham
Permalink | Reply | 0 comments |
headers
David Kastrup | 1 Jun 2009 11:37
X-Face
Picon
Picon

Re: [Issue?] hiding Accidental(s) on tied note(s) after a line break

Joe Neeman <joeneeman <at> gmail.com> writes:

[...]

>> p.s. Despite [As a result of?] banging my head against this
>> particular wall, I think I learned a little about Scheme +
>> Lilypond... that's some consolation!  =)
>
> If it's any additional consolation, your approach would have been
> perfectly ok were it not for the idiosyncrasies of Accidental.

Wouldn't it make more sense then first to apply his approach, and then
make sure that it actually works as intended?

It would appear to me that this would cause fewer surprises and
maintenance headaches in future.

It would appear that his approach was foiled by kinks in the current
implementation, and the long-term solution should prefer getting rid of
kinks rather than adding new ones.

Note that I don't have any actual knowledge of the code: it is just that
this conversation sets off my alarm bells.

--

-- 
David Kastrup
Permalink | Reply | 0 comments |
headers
Graham Percival | 1 Jun 2009 14:23
Picon
Favicon

Re: GUB on kainhofer: still cross/gcc

On Sun, May 31, 2009 at 09:20:24PM +0200, Jan Nieuwenhuizen wrote:
> diff --git a/gub/specs/darwin/odcctools.py b/gub/specs/darwin/odcctools.py
> index ee953c0..1d24944 100644

I'm getting very confused trying to figure out what file affects
the darwin-x86::cross/gcc compilations.  Candidates are:
- gub/specs/cross/gcc.py
- gub/specs/cross/gcc-core.py
- gub/specs/darwin/cross/gcc.py
- gub/specs/darwin/odcctools.py   (???)

I'm not convinced that GUB even knows which file to use; the build
commands contain "-O2 -g -g -O2 -O2  -O2 -g -g -O2".  Surely only
one "-O2 -g" matters?

Judging from that CompilerFlags page on the ubuntu wiki, I want to
add "CPPFLAGS=-D_FORTIFY_SOURCE=0" to one of those files.

Cheers,
- Graham
Permalink | Reply | 1 comment |
headers
Werner LEMBERG | 1 Jun 2009 12:53
Picon

bad formatting of lilypond grammar


The lilypond grammar contains some extremely long lines which look
very bad in formatting (and are difficult to comprehend), for example

  206 music_function_chord_body: music_function_identifier_musicless_prefix
                                 EXPECT_MUSIC function_arglist_nonmusic
                                 chord_body_element
  207                          | music_function_identifier_musicless_prefix
                                 function_arglist_nonmusic

Is it possible to fix the formatting so that lines are not exceeding
the 80 character length limit, as shown above?

    Werner
Permalink | Reply | 0 comments |
headers
Werner LEMBERG | 1 Jun 2009 13:16
Picon

beat grouping vs. beam grouping


In the docs there are references to both `beam-grouping' and
`beat-grouping'.  This is confusing.  However, `beam-grouping' doesn't
exist in the source code.  I thus suggest to replace `beam-grouping'
with `auto-beam beat-grouping' just to avoid the term `beam-grouping'
altogether.  The snippet `beam-grouping-in-7-8-time.ly' should
probably be renamed too.

    Werner
Permalink | Reply | 2 comments |
headers
Werner LEMBERG | 1 Jun 2009 15:06
Picon

setting `to-barline' for trills too?


Currently, `to-barline' is set to ##f for trills.  What about changing
it so that ##t is the default?

    Werner
Permalink | Reply | 0 comments |
headers
Carl D. Sorensen | 1 Jun 2009 18:13

Re: beat grouping vs. beam grouping


On 6/1/09 5:16 AM, "Werner LEMBERG" <wl <at> gnu.org> wrote:

> 
> 
> In the docs there are references to both `beam-grouping' and
> `beat-grouping'.  This is confusing.  However, `beam-grouping' doesn't
> exist in the source code.  I thus suggest to replace `beam-grouping'
> with `auto-beam beat-grouping' just to avoid the term `beam-grouping'
> altogether.  The snippet `beam-grouping-in-7-8-time.ly' should
> probably be renamed too.

A git grep for beam-grouping returned only the snippet you referenced above.

A git grep for "beam grouping" returned only one reference which was in the
snippet you referenced above.

Can you be more specific about where the doc references to beam-grouping
are?

Thanks,

Carl
Permalink | Reply | 1 comment |
headers
Peter Chubb | 2 Jun 2009 01:29
X-Face
Picon

Better MIDI


Hi,

  I've put up a page on how to get more realistic sounding MIDI output
  from current LilyPond, along with the scripts and scheme code used, at
  http://www.nicta.com.au/people/chubbp/articulate

  It has before-and-after MIDI samples to listen to, and a full
  description of what the script does and how to use it.

  Is there any way that the scheme code can be distributed with
  LilyPond?  It's fairly useful now, but could do with going over by
  some real experts for improvement. In particular I'd like to get rid
  of the double pass over all the notes (first to find out what to do
  then to do it), and the hacked up communication between the two
  passes.  I'd also like to do something about trills and turns with
  alterations, and do a better calculation for trill duration.

--
Dr Peter Chubb                              peter DOT chubb AT nicta.com.au
http://www.ertos.nicta.com.au           ERTOS within National ICT Australia
           Kernel Engineering Group (KEG): Where Systems Brew.
Permalink | Reply | 13 comments |
headers
Carl D. Sorensen | 2 Jun 2009 05:23

Re: Better MIDI


On 6/1/09 5:29 PM, "Peter Chubb" <lily.user <at> chubb.wattle.id.au> wrote:

> 
> 
> Hi,
> 
>   I've put up a page on how to get more realistic sounding MIDI output
>   from current LilyPond, along with the scripts and scheme code used, at
>   http://www.nicta.com.au/people/chubbp/articulate

Peter,

I haven't had a chance to look at your code, since I don't have a login to
your server, and it wasn't attached to your email to the list.

The improved MIDI sounded good to me.  I'd like to get it into the
distribution.

As a first step, it could be included in an optional add-in.  The way to
make it work is probably to first split your scheme and lilypond code.

I'd recommend that you put your scheme code in a new file that could be
placed in the scm/ directory, perhaps something
like articulation.scm.

And then you'll have your lilypond syntax stuff in articulation.ly file that
can be placed in the ly/ directory and included in a lilypond file.

Then, you can post your articulation.scm and articulation.ly files on the
(Continue reading)

Permalink | Reply | 1 comment |

Gmane