Re: [eigen] gcc 7.1 fails to build projects that depend on libeigen

[ Thread Index | Date Index | More lists.tuxfamily.org/eigen Archives ]


ah, nevermind, I initially thought it complained about any usage of enums as boolean, but that's only the case if the enum value is not 0 or 1, so here is the fix:

https://bitbucket.org/eigen/eigen/commits/c8d48daca9b9

gael.

On Sun, Jun 25, 2017 at 9:55 PM, Gael Guennebaud <gael.guennebaud@xxxxxxxxx> wrote:
Hi,

sorry for late replay, but that's not as easy as replacing them by static const bool, see for instance this old thread: http://eigen.tuxfamily.narkive.com/GatL7TiX/proposal-to-use-static-const-integer-class-members-instead-of-enum-values

So the current workaround is to disable this warning: -Wno-int-in-bool-context.

gael

On Fri, Jun 16, 2017 at 3:25 PM, Dmitry Rozhkov <dmitry.rozhkov@xxxxxxxxxxx.com> wrote:
Hi,

The latest gcc seems to have problems with traits based on enum. Please
 find in the attachment a typical build log (for sophus in this case).

What's the plan for them? Can we replace them with `static const bool`
rather than `enum`?

BR,
Dmitry




Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/