[odb-users] Internal Compiler Error in ODB 2.5.0-b.9 with Boost
becoggins at hotmail.com
Sat Feb 16 14:40:27 EST 2019
That update seems to have solved the sigfault problem!
However, do you have an updated odb-boost somewhere? The headers in /usr/local/include/odb/boost aren’t getting updated by bpkg and are still stuck at b3. bpkg can’t find an odb-boost package when I try to do it by hand, and I’m getting "incompatible odb interface version detected” when I attempt to compile against the old 2.5.0-b.3 headers.
The only problem I encountered when upgrading b9 to b11 was that the “bpkg uninstall --all --recursive” step in the instructions removes the ODB libraries, and that kills bpkg (which can’t find the ODB dylib). So I had to reinstall build2 at that point.
> On Feb 15, 2019, at 10:05 AM, Boris Kolpackov <boris at codesynthesis.com> wrote:
> Brian Coggins <becoggins at hotmail.com> writes:
>> I’m trying to use the latest ODB (2.5.0-b.9, downloaded and built today via
>> build2) to get c++17 support, and I’m running into that segfault people have
>> been reporting.
> I believe I have fixed that for the upcoming b.11 (but thanks for trying
> to get the backtrace).
> If you could try the latest staged version of ODB and confirm the fix,
> that would be great. I believe you can use the released build2 to upgrade
> and it should be as simple as:
> $ bpkg add https://stage.build2.org/1
> $ bpkg fetch
> $ bpkg build --upgrade --recursive
> $ ...
> Effectively the upgrade step from install-build2.xhtml.
> On the off chance the released build2 toolchain can't do this, you can
> fallback to getting staged build2 and use that; it's the same installation
> steps but the install script comes from here:
>  https://git.codesynthesis.com/cgit/odb/odb/commit/?id=3a1788234bfaa96ee093b68e9ba02cf7d5bdffe6
More information about the odb-users