Re: changes in chord names formatting (1503, 1572) (issue 4981052)

[Graham Percival]

On Fri, Nov 04, 2011 at 03:25:30PM +0000, Adam Spiers wrote:
> > I'm not beating myself up -- but when I see people spending
> > literally dozens of hours on tasks that could be automated with
> > 1-3 hours of programming, I hardly think that optimism is the
> > appropriate response.  :(
> 
> Given that we have this great opportunity to make things way better
> without too much effort, it seems an entirely appropriate response to
> me!  Surely you wouldn't prefer the automation to be very difficult,
> or even worse, impossible?

heh.

no, I'd prefer it if we had more people working on the automation,
or more people handling simple tasks so that advanced developers
(*cough* like me, if I may be so bold) could work on the
automation instead of handling those simple tasks, etc.

> > Incidently, the latest round of panic is because I switched to
> > ubuntu oneiric 11.10 instead of staying on 10.04 LTS.  I wanted
> > the gcc 4.6 toolchain for my Vivi work, but that's caused a huge
> > ripple of disruption in lilypond.
> 
> How come?  Lilypond compiles fine with gcc 4.6.1 on Fedora 15.

openssh renamed some function SSLv2_client_method, so curl won't
compile.  This is probably a 5-minute job to just download a newer
version of curl, but nobody's stepped forward yet.
(this relies on GUB, which is approximately 20,000 lines of python
which set up our binary building environemnt -- cross-compiling
for freebsd, darwin, mingw, and linux, all on linux)
http://code.google.com/p/lilypond/issues/detail?id=1998

we can't compile+run lilypond on 11.10 because of some weird
segfault.  We can avoid taht by compiling with -fno-crossjumping
-fkeep-inline-function, but apparently enabling the latter option
*breaks* some old testing code in flower/include/yaffut.h
http://code.google.com/p/lilypond/issues/detail?id=1997
http://code.google.com/p/lilypond/issues/detail?id=1875

You may find the latter two issues worthy of skimming.  I'm hoping
you do, because there's a non-zero chance that you'll recognize
some problem, or at least be curious enough to google around a
bit, and you may find a simple solution.  Or at least, having a
fresh pair of eyes on the problem can't hurt.

Of all these problems, the inability to compile (without weird
options) on ubuntu 11.10 is the worst, since that basically
eliminates the automation efforts I've been working on.

- Graham