Details
-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Developer Infrastructure
-
Labels:None
-
Story Points:2
-
Epic Link:
-
Sprint:Science Pipelines DM-S15-5
-
Team:Alert Production
Description
I created a new lsst package named "gcc" that contains Mario's gcc 4.8 package. I used it to build lsst_distrib on lsst-dev and it worked just fine. Unfortunately the package does not include bin/cc (which should be a symlink to bin/gcc), and this is wanted because the LSST build system uses cc to build C code.
The desired fix is to modify the installer to make a symlink bin/cc that points to bin/gcc.
Attachments
Issue Links
Activity
Merge to master. Now...how to make this usable by others?
The main thing is to allow "eups distrib install" to build things using this gcc without a lot of fuss on the user's part.
I would also help to add gcc to repos.yaml in lsstsw, so a user can "rebuild gcc". However, few people use lsstsw and I have no idea how to make Jenkins optionally build with this gcc, so this would not take us very far.
Right, you don't want anything to happen if a modern enough compiler is already available.
I think this package is in the same category as anaconda – it's not linked anywhere in the dependency chain, it's provided as a courtesy to those who try to develop on systems that are too old and cannot get an updated compiler otherwise.
At best, it should go into newinstall.sh – some code along the lines of "we've noticed you don't have gcc >= 4.8... it'd be really, really, really preferable and great if your sysadmin could install it... if they can't, we'll try building one for you."
+1 to Mario's comment.
Found the desktop link...