Phil Holmes <mail <at> philholmes.net> writes: > >> Phil Holmes <mail <at> philholmes.net> writes: > >>> /home/gub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org-- lilypond.git- > >>> release-unstable/lily/include/smobs.tcc:131: error: invalid operands of > >>> types 'scm_unused_struct* (Grob::*)()' and 'scm_unused_struct* > >>> (Smob_base<Grob>::*)()' to binary 'operator!='
This involves the address of a function in a templated class, the behavior of which didn't get resolved until C++ defect 115 and gcc 4.5.0 <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11407> We could probably use some other test to see if the base mark_smob() function has been redefined in the derived class ... or put the responsibility to register mark_smob() into each derived class. > OK: here's the result of a grep for gnu/gcc on the GUB machine: [...] > It looks like a bit of a mish-mash. But if we were going to upgrade from > what is mostly gcc 4.1.1/2, which version should we go to? Phil, How does the upgrade to gcc 4.8.2 look now ? The changes from Masamichi to librestrict look safe, and the later floating-point-endless-loop-eating-all-memory should be gone now that I've re-worked the skyline merge code. If gcc 4.8.2 still looks difficult, I'll look into problem with the templates. _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
