Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Please eliminate misleading warning when running scons on OSX with SIP

Description

On a Mac with OSX 10.11 and SIP enabled, every time I run scons on an LSST package I get the message:

$ scons scons: Reading SConscript files ... Could not import lsstcppimport; please ensure the base package has been built (not just setup). EUPS integration: enabled [etc]

It's not fatal, and is not indicative of a fundamental problem. But it is alarming, especially for new users who will assume this means something has broken when they first hit this message. (I did.)

Checklist

Lucidchart Diagrams

Issue Matrix

hide

Activity

Show:
Michael Wood-Vasey
August 2, 2017 at 9:39 AM

Merged to master.

Tim Jenness
August 2, 2017 at 8:10 AM

Looks fine to me. This is the technique sconsUtils uses to work out whether it has been imported in a SCons environment or not.

Michael Wood-Vasey
August 2, 2017 at 7:12 AM

I added a check to try to import SCons.Script if we can't import lsstcppimport. If we can import SCons.Script then we're in scons and we should worry about the failed import. If not, then still print out the warning.

The Jenkins job is #25718:

https://ci.lsst.codes/job/stack-os-matrix/25718

Tim Jenness
June 15, 2017 at 6:38 AM

I think you can probably see if Scons packages have been imported.

Robert Lupton
June 15, 2017 at 6:18 AM

It doesn't sound as if the introspection would be hard (would looking for LSST_LD_LIBRARY_PATH be enough?)

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Reviewers

Tim Jenness

Story Points

RubinTeam

Components

Checklist

Created January 29, 2016 at 10:15 AM
Updated August 2, 2017 at 9:39 AM
Resolved August 2, 2017 at 9:39 AM