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

loadLSST bug(s) for csh, ksh

    Details

    • Story Points:
      1
    • Team:
      SQuaRE

      Description

      A flaw in the v8.0 loadLSST scripts (and/or in eups/bin/setups) causes the following errors:

      1) When using ksh:

         $INSTALL_DIR/loadLSST.ksh
         ksh: /path/to/INSTALL_DIR/eups/bin/setups.ksh: cannot open [No such file or directory]
      

      And indeed, there is no eups/bin/setups.ksh file.

      2) When attempting to run the installation demo (v7.2.0.0):

         $> printenv SHELL
         /bin/tcsh
      

      [The same issue appears with csh, unsurprisingly.]

         $> source /path/to/install_dir/loadLSST.csh
         $> cd /path/to/demo
         $> setup obs_sdss
         $> ./bin/demo.sh
         ./bin/demo.sh: line 7:  /volumes/d0/lsst/stack80/eups/*default*/bin/setups.sh: No such file or directory
         ./bin/demo.sh: line 12: setup: command not found
      

      After hand-editing the demo.sh script to omit the "/default" string from the offending line, the demo runs normally to completion.

      Note that everything works fine for bash with v8.0, which is what I tested awhile back.

        Attachments

          Activity

          Hide
          ktl Kian-Tat Lim added a comment -

          I think that the first problem is intended to be fixed by removing loadLSST.ksh and any references to it since eups's setups.sh is intended to be used by all Posix shells.

          Show
          ktl Kian-Tat Lim added a comment - I think that the first problem is intended to be fixed by removing loadLSST.ksh and any references to it since eups's setups.sh is intended to be used by all Posix shells.
          Hide
          tjenness Tim Jenness added a comment -

          Is this ticket still relevant?

          Show
          tjenness Tim Jenness added a comment - Is this ticket still relevant?
          Hide
          tjenness Tim Jenness added a comment -

          With ksh and current Github newinstall.sh:

          $ ksh
          $ . ./loadLSST.ksh
          $ eups list lsst
             10.1-1-g84e9557+13 	current b1412 b1486 w_2015_26 b1471 setup
          $ source ./loadLSST.ksh
          $ source loadLSST.ksh
          ksh: .: loadLSST.ksh: cannot open [No such file or directory]
          $ . loadLSST.ksh
          ksh: .: loadLSST.ksh: cannot open [No such file or directory]
          

          So it does work if you use a full path to the .ksh file.

          Show
          tjenness Tim Jenness added a comment - With ksh and current Github newinstall.sh : $ ksh $ . ./loadLSST.ksh $ eups list lsst 10.1-1-g84e9557+13 current b1412 b1486 w_2015_26 b1471 setup $ source ./loadLSST.ksh $ source loadLSST.ksh ksh: .: loadLSST.ksh: cannot open [No such file or directory] $ . loadLSST.ksh ksh: .: loadLSST.ksh: cannot open [No such file or directory] So it does work if you use a full path to the .ksh file.
          Hide
          tjenness Tim Jenness added a comment -

          I have built v11.0_rc3 using csh and run the demo and it all works fine. ksh is now also fine so I think this has been fixed at some point in the past year. Closing for now.

          Show
          tjenness Tim Jenness added a comment - I have built v11.0_rc3 using csh and run the demo and it all works fine. ksh is now also fine so I think this has been fixed at some point in the past year. Closing for now.

            People

            • Assignee:
              Unassigned
              Reporter:
              shaw Richard Shaw [X] (Inactive)
              Watchers:
              Frossie Economou, Jonathan Sick, Kian-Tat Lim, Richard Shaw [X] (Inactive), Robyn Allsman [X] (Inactive), Tim Jenness
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Summary Panel