Bug 1312973 - vxl headers are not compliant with C++11
Summary: vxl headers are not compliant with C++11
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: vxl
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Igor Gnatenko
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1303377 1307273 1307855
TreeView+ depends on / blocked
 
Reported: 2016-02-29 16:38 UTC by Yaakov Selkowitz
Modified: 2017-08-08 13:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 13:05:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Yaakov Selkowitz 2016-02-29 16:38:56 UTC
Building a vxl-dependent package with (the now default) C++11 fails, e.g.:

In file included from /usr/include/vxl/vcl/vcl_compiler.h:237:0,
                 from /usr/include/vxl/vcl/vcl_iosfwd.h:8,
                 from /usr/include/vxl/core/vnl/vnl_matrix.h:36,
                 from /builddir/build/BUILD/DiffusionKurtosisFit-0.1.1/Code/Optimizer.h:3,
                 from /builddir/build/BUILD/DiffusionKurtosisFit-0.1.1/Code/Optimizer.cxx:3:
/usr/include/vxl/core/vnl/vnl_numeric_traits.h:387:60: error: 'constexpr' needed for in-class initialization of static data member 'const float vnl_numeric_traits<float>::zero' of non-integral type [-fpermissive]
   static const float zero VCL_STATIC_CONST_INIT_FLOAT_DECL(0.0F);
                                                            ^
and many more such errors.

A patch has been proposed here:

https://issues.itk.org/jira/browse/ITK-2976

Comment 1 Sebastian Pölsterl 2016-03-07 17:51:48 UTC
Also see https://github.com/vxl/vxl/commit/d4f530a98a67da310813f45af0f13901bf472981 and http://itk.org/gitweb?p=ITK.git;a=commit;h=a9329bfc80c10454730c9dd72e7202aa1665544d

We currently use -std=gnu++98 as a workaround to build InsightToolkit package.

Comment 2 Fedora Admin XMLRPC Client 2016-08-30 09:27:22 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora Admin XMLRPC Client 2016-08-30 09:43:11 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Fedora End Of Life 2017-07-25 20:16:02 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2017-08-08 13:05:10 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.