On Tue, May 13, 2014 at 04:21:19PM +1000, Graeme Lee wrote:
> On 13-May 8:33, Matthias Kilian wrote:
> >Could anyone with enough spare time try to - run make configure on i386 -
> >run make configure on whatever platform still uses gcc-3.3? [...]
> I've re-done the update. This one includes updated snprintf patches, and
> the gcc 3.3.5 patch.
Still not using ${MODPY_INCDIR}, and (untested) the gcc requirement
checks in the autoconf goo are missing,
Also, you patched aclocal.m4, but for lilypond that's *generated*
from snippets in stepmake/* (at least it was in the past, and looking
at the 2.18 sources, it still does). Yes, another level of
auto-generated files on top of autoconf, isn't it nice? ;-)
The lilypond people are aware that it sucks, but nobody wants to
take the tort^Wpleasure improving the lilypond build system.
(But don't step in and bake more diffs for now, I'm working on it)
> The documentation extraction, though is weird. The tarball does not include
> /offline-root/ so the build fails with it in the makefiles. I would like to
> know the correct way of handling this for both now and future reference.
The documentation is copied from the documentation distfile, not
from built documentation (we can't build the documentation ourselves,
because our makeinfo is too old -- I sent a makeinfo port some time
ago, but it had some issues so in never committed it).
For lilypond-2.14, the documentation distfile had the offline-root
directories, but this has changed for lilypond-2.18.
Ciao,
Kili
