Re: GUB fail with smob templates
How does the upgrade to gcc 4.8.2 look now ? Just wondering: There is already a gcc 4.9.x series, so why are we trying to update to 4.8.x? In this branch, I've tried gcc-4.9. https://github.com/trueroad/gub/tree/gcc-4.9 I've succeed to build lilypond-installer for mingw, linux-x86, linux-64, freebsd-x86, freebsd-64 platforms. And they work fine. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB fail with smob templates
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. Now, in this branch, https://github.com/trueroad/gub/tree/gcc-4.8 The following commands have been succeed by gcc-4.8.2. bin/gub mingw::lilypond-installer bin/gub linux-x86::lilypond-installer bin/gub linux-64::lilypond-installer bin/gub freebsd-x86::lilypond-installer bin/gub freebsd-64::lilypond-insatller They work fine in my environments. mingw: bad_alloc don't occur. freebsd-x86: SIGSEGV don't occur. Correct PDFs are generated. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB fail with smob templates
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_baseGrob::*)()' 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 lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB fail with smob templates
How does the upgrade to gcc 4.8.2 look now ? Just wondering: There is already a gcc 4.9.x series, so why are we trying to update to 4.8.x? Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB fail with smob templates
- Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Cc: lilypond-devel@gnu.org Sent: Sunday, October 12, 2014 6:41 PM Subject: Re: GUB fail with smob templates Phil Holmes m...@philholmes.net writes: GUB has again coughed on the changes to the SMOB code. It's well out of my depth to understand why, but I've pasted below some of the error messages: the make is built with -j14, so I presume that's why there are so many. /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_baseGrob::*)()' to binary 'operator!=' I've pushed a prospective fix to staging. No idea whether it will do the trick. -- David Kastrup This failed again. I've attached a zip of the whole logfile. I'll be around for most of today, so can test any potential fix quite quickly. I'll also look at how GCC could be updated. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB fail with smob templates
- Original Message - From: Phil Holmes m...@philholmes.net To: David Kastrup d...@gnu.org Cc: lilypond-devel@gnu.org Sent: Tuesday, October 14, 2014 10:03 AM Subject: Re: GUB fail with smob templates - Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Cc: lilypond-devel@gnu.org Sent: Sunday, October 12, 2014 6:41 PM Subject: Re: GUB fail with smob templates Phil Holmes m...@philholmes.net writes: GUB has again coughed on the changes to the SMOB code. It's well out of my depth to understand why, but I've pasted below some of the error messages: the make is built with -j14, so I presume that's why there are so many. /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_baseGrob::*)()' to binary 'operator!=' I've pushed a prospective fix to staging. No idea whether it will do the trick. -- David Kastrup This failed again. I've attached a zip of the whole logfile. I'll be around for most of today, so can test any potential fix quite quickly. I'll also look at how GCC could be updated. -- Phil Holmes OK: here's the result of a grep for gnu/gcc on the GUB machine: specs/cross/gcc-2-95.py: source = 'http://ftp.gnu.org/pub/gnu/gcc/gcc-2.95.3/gcc-everything-2.95.3.tar.gz' specs/cross/gcc-core.py: source = 'http://ftp.gnu.org/pub/gnu/gcc/gcc-4.1.1/gcc-4.1.1.tar.bz2' specs/cross/gcc.py: source = 'http://ftp.gnu.org/pub/gnu/gcc/gcc-4.1.2/gcc-4.1.2.tar.bz2' specs/cross/gcc.py: source = 'http://ftp.gnu.org/pub/gnu/gcc/gcc-4.1.1/gcc-4.1.1.tar.bz2' specs/cygwin/cross/gcc.py:# source = 'http://ftp.gnu.org/pub/gnu/gcc/gcc-4.1.2/gcc-4.1.2.tar.bz2' specs/cygwin/cross/gcc.py: source = 'http://ftp.gnu.org/pub/gnu/gcc/gcc-4.3.4/gcc-4.3.4.tar.bz2' specs/cygwin/cross/gcc.py: source = 'http://ftp.gnu.org/pub/gnu/gcc/gcc-3.4.4/gcc-3.4.4.tar.bz2' specs/debian/cross/gcc.py: source = 'http://ftp.gnu.org/pub/gnu/gcc/gcc-' + debian.gcc_version + '/gcc-' + debian.gcc_version + '.tar.bz2' specs/debian/cross/gcc.py: source = 'http://ftp.gnu.org/pub/gnu/gcc/gcc-3.4.6/gcc-3.4.6.tar.bz2' specs/freebsd/cross/gcc.py: source = 'http://ftp.gnu.org/pub/gnu/gcc/gcc-4.3.2/gcc-4.3.2.tar.bz2' specs/gcc.py: source = 'http://ftp.gnu.org/pub/gnu/gcc/gcc-4.1.2/gcc-4.1.2.tar.bz2' specs/linux-arm-softfloat/cross/gcc-core.py: source = 'http://ftp.gnu.org/pub/gnu/gcc/gcc-3.4.6/gcc-3.4.6.tar.bz2' specs/linux-arm-softfloat/cross/gcc.py: source = 'http://ftp.gnu.org/pub/gnu/gcc/gcc-3.4.6/gcc-3.4.6.tar.bz2' 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 Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB fail with smob templates
Phil Holmes m...@philholmes.net writes: - Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Cc: lilypond-devel@gnu.org Sent: Sunday, October 12, 2014 6:41 PM Subject: Re: GUB fail with smob templates Phil Holmes m...@philholmes.net writes: GUB has again coughed on the changes to the SMOB code. It's well out of my depth to understand why, but I've pasted below some of the error messages: the make is built with -j14, so I presume that's why there are so many. /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_baseGrob::*)()' to binary 'operator!=' I've pushed a prospective fix to staging. No idea whether it will do the trick. -- David Kastrup Zip attached. /home/gub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/include/smobs.tcc:133: error: invalid operands of types 'scm_unused_struct* (Smob_baseSkyline_pair::*)()' and 'scm_unused_struct* (Skyline_pair::*)()' to binary 'operator!=' This is getting absolutely ridiculous, but I pushed another fix to staging (basically, I now have to cast a member function pointer to its own type before comparing it with another member function pointer cast to its type). With regard to upgrading gcc versions, I think that the latest 4.8 version of gcc should be a reasonably safe bet. However, I don't know whether darwin-ppc is still a supported platform for it. One would probably have to take the last supported version. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB fail with smob templates
- Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net This is getting absolutely ridiculous, but I pushed another fix to staging (basically, I now have to cast a member function pointer to its own type before comparing it with another member function pointer cast to its type). OK: I'm running patchy-staging now and will tryu again once the fix is in master. With regard to upgrading gcc versions, I think that the latest 4.8 version of gcc should be a reasonably safe bet. However, I don't know whether darwin-ppc is still a supported platform for it. One would probably have to take the last supported version. I'll do some research on the ppc and once I've tried this fix, I'll look at upgrading GUB. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB fail with smob templates
Phil Holmes m...@philholmes.net writes: - Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Cc: lilypond-devel@gnu.org Sent: Tuesday, October 14, 2014 12:16 PM Subject: Re: GUB fail with smob templates Phil Holmes m...@philholmes.net writes: - Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Cc: lilypond-devel@gnu.org Sent: Sunday, October 12, 2014 6:41 PM Subject: Re: GUB fail with smob templates Phil Holmes m...@philholmes.net writes: GUB has again coughed on the changes to the SMOB code. It's well out of my depth to understand why, but I've pasted below some of the error messages: the make is built with -j14, so I presume that's why there are so many. /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_baseGrob::*)()' to binary 'operator!=' I've pushed a prospective fix to staging. No idea whether it will do the trick. -- David Kastrup Zip attached. /home/gub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/include/smobs.tcc:133: error: invalid operands of types 'scm_unused_struct* (Smob_baseSkyline_pair::*)()' and 'scm_unused_struct* (Skyline_pair::*)()' to binary 'operator!=' This is getting absolutely ridiculous, but I pushed another fix to staging (basically, I now have to cast a member function pointer to its own type before comparing it with another member function pointer cast to its type). Fails compiling for a different target now. Logfile attached again. /home/gub/gub/target/freebsd-64/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/include/smobs.tcc:136: error: invalid operands of types 'bool' and 'int' to binary 'operator==' So now we cannot compare a bool with an int? What is this, Pascal? The error message also does not fit the current line in smobs.tcc: 136 if (static_castSCM (Super::*)()(Super::mark_smob) != 137 static_castSCM (Super::*)()(Smob_baseSuper::mark_smob)) Previous versions had 136 if (Super::type_p_name_ != 0) which is still not the best fit, but at least there is an integer involved. Do you reckon we should continue to try to get this fixed, or just bite the bullet and update gcc and see if that works? It would appear that the versions of GCC are somewhat basic regarding their template support. Now what is really surprising to me is that 2.19.15 went ahead without much of a hitch. Because the changes of 2.19.16, as compared to 2.19.15, seem to be more on the surface. Since we _did_ get 2.19.15 through, 2.19.16 should be a breeze. However, the current batch of error messages is totally baffling to me. The current error messages just do not appear to match the flagged lines at all. So I'm poking around quite in the dark. It's probably silly to ask since you are not building for the first time, but you are sure that you are working from the current origin/release/unstable ? To me it looks like updating gcc to some newer version might make sense. Starting with version 2.19.15, we are relying more on templates than before. And working with gcc versions that go bonkers in entirely puzzling ways is likely going to cause more trouble than the one we are having right now anyway. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB fail with smob templates
- Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Fails compiling for a different target now. Logfile attached again. /home/gub/gub/target/freebsd-64/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/include/smobs.tcc:136: error: invalid operands of types 'bool' and 'int' to binary 'operator==' So now we cannot compare a bool with an int? What is this, Pascal? The error message also does not fit the current line in smobs.tcc: 136 if (static_castSCM (Super::*)()(Super::mark_smob) != 137 static_castSCM (Super::*)()(Smob_baseSuper::mark_smob)) Previous versions had 136 if (Super::type_p_name_ != 0) which is still not the best fit, but at least there is an integer involved. I agree with what you say about the strange error message. Just to confirm, though: lines 136-7 as given in the error message are the lines to be found in smobs.tcc. Do you reckon we should continue to try to get this fixed, or just bite the bullet and update gcc and see if that works? It would appear that the versions of GCC are somewhat basic regarding their template support. Now what is really surprising to me is that 2.19.15 went ahead without much of a hitch. Because the changes of 2.19.16, as compared to 2.19.15, seem to be more on the surface. Since we _did_ get 2.19.15 through, 2.19.16 should be a breeze. However, the current batch of error messages is totally baffling to me. The current error messages just do not appear to match the flagged lines at all. So I'm poking around quite in the dark. It's probably silly to ask since you are not building for the first time, but you are sure that you are working from the current origin/release/unstable ? Had me worried. I checked and I am. To me it looks like updating gcc to some newer version might make sense. Starting with version 2.19.15, we are relying more on templates than before. And working with gcc versions that go bonkers in entirely puzzling ways is likely going to cause more trouble than the one we are having right now anyway. I'll start looking at it now. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB fail with smob templates
Phil Holmes m...@philholmes.net writes: GUB has again coughed on the changes to the SMOB code. It's well out of my depth to understand why, but I've pasted below some of the error messages: the make is built with -j14, so I presume that's why there are so many. /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_baseGrob::*)()' to binary 'operator!=' What a crock. Do we have a reasonably fast way to get to these error messages? I can apply a patch trying to get across this error message (and its relatives), but I don't really know whether it will do the trick with the old gcc version we appear to be using here. Or is there a reasonable chance of moving GUB to a newer version of GCC? I think we are older than most C++ compilers by now. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB fail with smob templates
Phil Holmes m...@philholmes.net writes: GUB has again coughed on the changes to the SMOB code. It's well out of my depth to understand why, but I've pasted below some of the error messages: the make is built with -j14, so I presume that's why there are so many. /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_baseGrob::*)()' to binary 'operator!=' I've pushed a prospective fix to staging. No idea whether it will do the trick. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB fail with smob templates
I'll try to see whether this is successful tomorrow afternoon. -- Phil Holmes - Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Cc: lilypond-devel@gnu.org Sent: Sunday, October 12, 2014 6:41 PM Subject: Re: GUB fail with smob templates Phil Holmes m...@philholmes.net writes: GUB has again coughed on the changes to the SMOB code. It's well out of my depth to understand why, but I've pasted below some of the error messages: the make is built with -j14, so I presume that's why there are so many. /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_baseGrob::*)()' to binary 'operator!=' I've pushed a prospective fix to staging. No idea whether it will do the trick. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB fail with smob templates
Phil Holmes m...@philholmes.net writes: GUB failed today with the following errors: /home/gub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org--lilypond.git- release-unstable/lily/include/unpure-pure-container.hh: In static member function 'static scm_unused_struct* Unpure_pure_container::make_smob (scm_unused_struct*, scm_unused_struct*)': /home/gub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org--lilypond.git- release-unstable/lily/include/unpure-pure-container.hh:39: error: 'templateclass Super class Smob2' used without template parameters /home/gub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org--lilypond.git- release-unstable/lily/include/unpure-pure-container.hh:40: error: 'templateclass Super class Smob2' used without template parameters I assume this is http://code.google.com/p/lilypond/issues/detail?id=4082 The actually flagged code is in issue 4086 instead, though 4086 heavily depends on 4082. but it's way over my head to know what the problem is. Possibly an older gcc version. Are these the only errors? In a parallel build, one would expect to run across several errors in different files before compilation bombs out. Would be good to know and/or have some further complaints to look at. I'll try brooding over the error messages and see whether they suggest some syntax that might be more palatable to older gcc versions. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB fail with smob templates
David Kastrup d...@gnu.org writes: Phil Holmes m...@philholmes.net writes: GUB failed today with the following errors: /home/gub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org--lilypond.git- release-unstable/lily/include/unpure-pure-container.hh: In static member function 'static scm_unused_struct* Unpure_pure_container::make_smob (scm_unused_struct*, scm_unused_struct*)': /home/gub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org--lilypond.git- release-unstable/lily/include/unpure-pure-container.hh:39: error: 'templateclass Super class Smob2' used without template parameters /home/gub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org--lilypond.git- release-unstable/lily/include/unpure-pure-container.hh:40: error: 'templateclass Super class Smob2' used without template parameters I assume this is http://code.google.com/p/lilypond/issues/detail?id=4082 The actually flagged code is in issue 4086 instead, though 4086 heavily depends on 4082. but it's way over my head to know what the problem is. Possibly an older gcc version. Are these the only errors? In a parallel build, one would expect to run across several errors in different files before compilation bombs out. Would be good to know and/or have some further complaints to look at. I'll try brooding over the error messages and see whether they suggest some syntax that might be more palatable to older gcc versions. Pushed a matching fix. It does not appear that this particular problem is coded elsewhere. I think that the compiler complaint might be correct even though my newer GCC variant does not bother mentioning it. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB fail with smob templates
- Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Cc: lilypond-devel@gnu.org Sent: Sunday, September 14, 2014 4:50 PM Subject: Re: GUB fail with smob templates David Kastrup d...@gnu.org writes: Phil Holmes m...@philholmes.net writes: GUB failed today with the following errors: /home/gub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org--lilypond.git- release-unstable/lily/include/unpure-pure-container.hh: In static member function 'static scm_unused_struct* Unpure_pure_container::make_smob (scm_unused_struct*, scm_unused_struct*)': /home/gub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org--lilypond.git- release-unstable/lily/include/unpure-pure-container.hh:39: error: 'templateclass Super class Smob2' used without template parameters /home/gub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org--lilypond.git- release-unstable/lily/include/unpure-pure-container.hh:40: error: 'templateclass Super class Smob2' used without template parameters I assume this is http://code.google.com/p/lilypond/issues/detail?id=4082 The actually flagged code is in issue 4086 instead, though 4086 heavily depends on 4082. but it's way over my head to know what the problem is. Possibly an older gcc version. Are these the only errors? In a parallel build, one would expect to run across several errors in different files before compilation bombs out. Would be good to know and/or have some further complaints to look at. I'll try brooding over the error messages and see whether they suggest some syntax that might be more palatable to older gcc versions. Pushed a matching fix. It does not appear that this particular problem is coded elsewhere. I think that the compiler complaint might be correct even though my newer GCC variant does not bother mentioning it. I'll run patchy-staging and try to restart GUB. Unlikely there will be an upload today, though: likely I'll go tomorrow. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
