View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004453Slicer4Core: Base Codepublic2017-10-05 16:402017-10-06 11:18
Reporterpieper Assigned Tojcfr  
PrioritynormalSeverityblockReproducibilityalways
Status closedResolutionno change required 
PlatformlinuxOSubuntuOS Version16.04.2
Product Version 
Target VersionFixed in VersionSlicer 4.7.0 
Summary0004453: numpy build error - patch failed
Description

gcc 5.4.0

Steps To Reproduce

Normal build results in error below.

Additional Information
[ 96%] Performing patch step for 'NUMPY'
-- Applying 'numpy-01-system_info-fix-clang.patch' - failed
CMake Error at /home/pieper/slicer4/latest/Slicer/CMake/SlicerPatch.cmake:54 (message):
  Reversed (or previously applied) patch detected! Assume -R? [n]

  Apply anyway? [n]

  2 out of 2 hunks ignored -- saving rejects to file
  numpy/distutils/system_info.py.rej

CMakeFiles/NUMPY.dir/build.make:101: recipe for target 'NUMPY-prefix/src/NUMPY-stamp/NUMPY-patch' failed
make[3]: *** [NUMPY-prefix/src/NUMPY-stamp/NUMPY-patch] Error 1
CMakeFiles/Makefile2:1866: recipe for target 'CMakeFiles/NUMPY.dir/all' failed
make[2]: *** [CMakeFiles/NUMPY.dir/all] Error 2
CMakeFiles/Makefile2:1878: recipe for target 'CMakeFiles/NUMPY.dir/rule' failed
make[1]: *** [CMakeFiles/NUMPY.dir/rule] Error 2
Makefile:740: recipe for target 'NUMPY' failed
make: *** [NUMPY] Error 2
TagsNo tags attached.

Relationships

related to 0004452 resolvedjcfr numpy build error - looks for fortran compiler 

Activities

jcfr

jcfr

2017-10-05 16:48

administrator   ~0015259

Is this a clean build ?

Can you remove numpy and reconfigure:

rm -rf numpy*.applied
rm -rf  NUMPY*
pieper

pieper

2017-10-05 16:56

administrator   ~0015264

Yes, deleting NUMPY* resolved the issue.

Probably cause: numpy.*.applied did not exist, but does exist now after the fresh rebuild.
pieper

pieper

2017-10-05 16:59

administrator   ~0015265

By the way, thanks!
pieper

pieper

2017-10-06 09:45

administrator   ~0015267

A check could be put in place for this case, but I'm closing this since it appears to only be a transient issue impacting people doing incremental rebuilds and the workaround is documented.
jcfr

jcfr

2017-10-06 11:18

administrator   ~0015268

A check could be put in place for this case

Indeed, that said incremental rebuild are expected to work after switching to version >= r26337
See http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=26337

Issue History

Date Modified Username Field Change
2017-10-05 16:40 pieper New Issue
2017-10-05 16:40 pieper Status new => assigned
2017-10-05 16:40 pieper Assigned To => jcfr
2017-10-05 16:40 pieper Issue generated from: 0004452
2017-10-05 16:40 pieper Relationship added related to 0004452
2017-10-05 16:46 jcfr Additional Information Updated View Revisions
2017-10-05 16:48 jcfr Note Added: 0015259
2017-10-05 16:56 pieper Note Added: 0015264
2017-10-05 16:59 pieper Note Added: 0015265
2017-10-05 17:44 jcfr Status assigned => resolved
2017-10-05 17:44 jcfr Resolution open => no change required
2017-10-05 17:44 jcfr Fixed in Version => Slicer 4.7.0
2017-10-06 09:45 pieper Status resolved => closed
2017-10-06 09:45 pieper Note Added: 0015267
2017-10-06 11:18 jcfr Note Added: 0015268