View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004612 | Slicer4 | Core: Building (CMake, Superbuild) | public | 2018-09-18 02:51 | 2020-01-23 08:07 |
Reporter | torquil | Assigned To | jcfr | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Platform | Linux | OS | Debian | OS Version | Sid |
Product Version | |||||
Target Version | Slicer 4.11.0 | Fixed in Version | Slicer 4.11.0 | ||
Summary | 0004612: Build error with GCC/G++ 8.2.0 | ||||
Description | When building Slicer Git Master with GCC/G++ 8.2.0, the build fails with a segmentation fault: <pre> It seems that Slicer Git Master uses Python 2.7.13. Could it be related to this?: In that case, perhaps this has been fixed in a newer version of Python 2.7? | ||||
Steps To Reproduce | To reproduce, build Slicer Git Master on Debian Sid Linux using GCC 8.2.0, using the following commands: cmake -DCMAKE_VERBOSE_MAKEFILE:BOOL=1 -DCMAKE_BUILD_TYPE:STRING=Release \ make VERBOSE=1 -j1 | ||||
Additional Information | $ gcc --version $ g++ --version | ||||
Tags | No tags attached. | ||||
Thanks for the detailed report. Could you try to use the latest python2 instead of 2.7.13 to see if this solves it? Change 2.7.13 for 2.7.15 in these 2 lines in your SuperBuild/External_python.cmake source folder https://github.com/Slicer/Slicer/blob/master/SuperBuild/External_python.cmake#L56-L59 And the URL_MD5 to: "045fb3440219a1f6923fefdabde63342":
And rebuild. I am testing it too. |
|
I tested it, and hitting this bug: https://github.com/python-cmake-buildsystem/python-cmake-buildsystem/issues/224 I am going to disable nis using this branch: https://github.com/phcerdan/python-cmake-buildsystem/commit/a0ba1dc557d870e625e4a03373f3fb2a9f42d9fb My work in progress to update python is in this branch: https://github.com/phcerdan/Slicer/tree/update_python |
|
I tested with 2.7.15, and it built fine. When I try to start Slicer I built, I get a segmentation fault, but that might be unrelated to the Python problem (I also got it earlier when I managed to build Slicer using the system Python installation): When running SlicerApp-real in gdb: $ cd Slicer-Superbuild-Release/Slicer-build/bin Starting program: /home/torquil/src/upstream/slicer/Slicer-Superbuild-Release/Slicer-build/bin/SlicerApp-real Thread 1 "SlicerApp-real" received signal SIGSEGV, Segmentation fault. But I can report this in a different bug report, unless you immediately know what causes it? :-) At least the building works for me now. |
|
This will be fixed as soon as the following PR is integrated: https://github.com/python-cmake-buildsystem/python-cmake-buildsystem/pull/263 |
|
Fixed in r28743 |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2018-09-18 02:51 | torquil | New Issue | |
2018-09-18 02:51 | torquil | Status | new => assigned |
2018-09-18 02:51 | torquil | Assigned To | => jcfr |
2018-09-18 13:31 | phcerdan | Note Added: 0016025 | |
2018-09-18 13:32 | phcerdan | Note Edited: 0016025 | View Revisions |
2018-09-18 19:25 | phcerdan | Note Edited: 0016025 | View Revisions |
2018-09-18 20:09 | phcerdan | Note Added: 0016029 | |
2018-09-19 00:32 | torquil | Note Added: 0016031 | |
2018-10-16 06:48 | jcfr | Description Updated | View Revisions |
2018-10-16 06:48 | jcfr | Description Updated | View Revisions |
2018-10-16 06:49 | jcfr | Target Version | => Slicer 4.11.0 |
2020-01-22 12:14 | jcfr | Note Added: 0016304 | |
2020-01-23 08:07 | jcfr | Status | assigned => resolved |
2020-01-23 08:07 | jcfr | Resolution | open => fixed |
2020-01-23 08:07 | jcfr | Fixed in Version | => Slicer 4.11.0 |
2020-01-23 08:07 | jcfr | Note Added: 0016307 |