Jay Anderson <horndud...@gmail.com> writes: > On Tue, Jan 3, 2012 at 1:12 AM, m...@apollinemike.com > <m...@apollinemike.com> wrote: >> On Jan 3, 2012, at 9:02 AM, David Kastrup wrote: >>> If he hadn't rerun configure since before version 2.15.21, I think that >>> the compilation would likely have failed for other reasons. The problem >>> report is for 2.15.23. It may be worth for him to report the CXXFLAGS >>> setting in config.status just to be on the safe side, but I consider it >>> unlikely that this particular problem has not already been covered. >>> > > I pulled down lilypond and build new just last week. > > CXXFLAGS in config.status is: > - With optimization (default): "O2 -finline-functions -g -pipe > -fno-optimize-sibling-calls" > - Without optimization: "-g -pipe -fno-optimize-sibling-calls" > >> Are you using an optimized binary? Mine is unoptimized. Please try >> ./autogen.sh --disable-optimizing before compiling and let me know >> if that makes the segfault go away. > > I found --disable-optimising instead. Same result. > > I can't reproduce this on my wife's mac or on my laptop (also running > ubuntu 11.10). The only difference I can think of is I'm running > 64-bit and my laptop is 32-bit. Unless someone else can reproduce this > issue don't spend much more time on this.
Can you use git bisect for identifying the commit where things go wrong for you? > I have a good solution (adding in the dynamics). Thanks! That sounds like a workaround rather than a solution. It would be good to find the actual reason. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
