According to our current buildbot status, this seems to happen not just with gcc
5.4 but with all Linux 64-bit compilers.
The comment about this getting fixed with the next version is already a bit old
(2016), so I'm not sure if we should hold our breath for it. So I think it would
be good if we could get rid of the warning on our end. As far as I understand,
there is no good way for us to address the root cause of this, and it does
affect what will become our standard build (Linux, 64-bit).
Some options:
- Try to silence the warning or filter it out.
- Detect the warning and add some output that explains why it can be ignored,
pointing to this issue.
- See if we can avoid the warning by using different linker options.
Regarding the last point, I wonder if we should give up on the idea of forcing a
static build and should instead go with the system default everywhere. Many of
the build issues and complications we have when using CPLEX, OSI etc. seem to be
related to the fact that we want to do a custom thing. If it helps avoid
warnings, simplify the setup instructions and CMake file and would allow us to
use more vanilla configurations of the libraries we use, I wouldn't mind some
mild performance loss. (We should measure first.)
Anyone willing to look into this?
|