On Thu, Aug 7, 2014, at 12:15 PM, Ken Moffat wrote:
Dropping back to 2.3.1 fixed it. One of my colleagues created a patch to locally revert that particular change in libsigc++ which also fixed the build.
My first question [ at last! ] is: Do you care about people who build 0.48 with libsigc++-2.3-series ? If you do, any ideas how to fix this ?
One note on this. I believe that the 'care' aspect is definitely present. The main question would be as to who on our side has time to spare to focus on it. Keeping forwards compatible is a good thing, but we do have more limited resources in terms of man-hours and people.
So please do not feel slighted if it takes some time to respond to individual aspects. We definitely are interested in improving our codebase and support.