On 2009-10-03, Jan Nieuwenhuizen wrote: > Op donderdag 01-10-2009 om 14:37 uur [tijdzone -0700], schreef Patrick > McCarty: > > > to see if that would fix it, but for some reason I couldn't get that > > working; my normal method of adding "patches = [...]" didn't work. > > GUB just seemed to skip over the "patches = [...]" line and only > > applied the substitutions in the "patch" function. > > patches are applied by the patch () function, see gub/build.py. > If you override the patch function, *.AutoBuild.patch (self) > must be called. See examples in other .py files. > > It is good practice to do so even if there are no patches in > a class [yet].
Thanks! I managed to get the patch applied against gcc 4.3.2, but it didn't fix my issue in the end. Same compile failure. I'll keep investigating. :-) Thanks, Patrick _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
