Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-10272

scons build fails under miniconda3 on el6

    Details

      Description

      We are unable to build on el6/py3 as the scons product's eupspkg.cfg.sh references python2.7. The system python interpreter on el6 is python2.6. If scons is still compatible with 2.6, and we want to support the combination of el6/py3 (???), this could be fixed by changing the interpreter to be python2.

      [el6] ***** error: from /build/EupsBuildDir/Linux64/scons-2.5.0.lsst2+1/build.log:
      [el6] ++ debug 'CC='\''cc'\'''
      [el6] ++ [[ 3 -ge 2 ]]
      [el6] ++ echo 'eupspkg.dumpvar (debug): CC='\''cc'\'''
      [el6] eupspkg.dumpvar (debug): CC='cc'
      [el6] + for _VAR in '"$@"'
      [el6] + eval 'debug "CXX='\''$CXX'\''"'
      [el6] ++ debug 'CXX='\''c++'\'''
      [el6] ++ [[ 3 -ge 2 ]]
      [el6] ++ echo 'eupspkg.dumpvar (debug): CXX='\''c++'\'''
      [el6] eupspkg.dumpvar (debug): CXX='c++'
      [el6] + for _VAR in '"$@"'
      [el6] + eval 'debug "SCONSFLAGS='\''$SCONSFLAGS'\''"'
      [el6] ++ debug 'SCONSFLAGS='\''opt=3'\'''
      [el6] ++ [[ 3 -ge 2 ]]
      [el6] ++ echo 'eupspkg.dumpvar (debug): SCONSFLAGS='\''opt=3'\'''
      [el6] eupspkg.dumpvar (debug): SCONSFLAGS='opt=3'
      [el6] + build
      [el6] + python2.7 setup.py build
      [el6] /build/EupsBuildDir/Linux64/scons-2.5.0.lsst2+1/scons-2.5.0.lsst2+1/ups/eupspkg.cfg.sh: line 5: python2.7: command not found
      [el6] + exit -4
      [el6] eups distrib: Failed to build scons-2.5.0.lsst2+1.eupspkg: Command:
      [el6] 	source "/build/eups/bin/setups.sh"; export EUPS_PATH="/build"; (/build/EupsBuildDir/Linux64/scons-2.5.0.lsst2+1/build.sh) >> /build/EupsBuildDir/Linux64/scons-2.5.0.lsst2+1/build.log 2>&1 4>/build/EupsBuildDir/Linux64/scons-2.5.0.lsst2+1/build.msg 
      [el6] exited with code 252
      [el6] Removing lockfile /build/.lockDir/exclusive-root.631
      

        Attachments

          Issue Links

            Activity

            Hide
            tjenness Tim Jenness added a comment - - edited

            I endorse replacing the -6.py2 Jenkins build with a -6.py3 one. No point having two py2 builds. Only need one on centos7 to ensure we aren't breaking things.

            Show
            tjenness Tim Jenness added a comment - - edited I endorse replacing the -6.py2 Jenkins build with a -6.py3 one. No point having two py2 builds. Only need one on centos7 to ensure we aren't breaking things.
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            Per discussion with @frossie, I've moved the v14 tag on the scons repo.

            Show
            jhoblitt Joshua Hoblitt added a comment - Per discussion with @frossie, I've moved the v14 tag on the scons repo.
            Show
            jhoblitt Joshua Hoblitt added a comment - Testing centos-6.py3: https://ci.lsst.codes/blue/organizations/jenkins/stack-os-matrix/detail/stack-os-matrix/26755/pipeline/
            Show
            jhoblitt Joshua Hoblitt added a comment - Take 2: https://ci.lsst.codes/blue/organizations/jenkins/stack-os-matrix/detail/stack-os-matrix/26756/pipeline/
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            This issue appears to have been completely resolved by DM-8560.

            Show
            jhoblitt Joshua Hoblitt added a comment - This issue appears to have been completely resolved by DM-8560 .

              People

              • Assignee:
                jhoblitt Joshua Hoblitt
                Reporter:
                jhoblitt Joshua Hoblitt
                Watchers:
                Joshua Hoblitt, Tim Jenness
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: