Project

General

Profile

Feature #13393

Setup "cc" soft link and CC/CXX/FC environment variables for gcc product

Added by Ben Morgan about 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
-
Start date:
08/02/2016
Due date:
% Done:

100%

Estimated time:
2.00 h
Spent time:
Co-Assignees:
Duration:

Description

The gcc product currently does not contain the cc softlink to gcc. The cc name for the system C compiler is often checked for first by build tools like CMake/Autotools and may cause a mixture of UPS/system compilers to be discovered at configure time if it's absent. Adding the soft link would follow typical Linux conventions for packaging GCC.

It would also be useful to have the gcc UPS product set the CC, CXX and FC environment variables when setup to the full paths to the product's gcc, g++ and gfortran compilers. These are useful as build tools, even plain Make, will pick these variables up by default, helping to create a consistent and portable build environment.

History

#1 Updated by Kyle Knoepfel about 3 years ago

  • Status changed from New to Feedback

We see no problem in creating the softlinks--in addition to cc, we would also provide the c++ and f95 softlinks.

However, we prefer to not export the environment variables that you request: doing so would adjust the default behavior of cmake and possibly other utilities (e.g. user-written make files). If you would like to argue for that aspect of this feature request, please bring it up at a stakeholders' meeting.

#2 Updated by Ben Morgan about 3 years ago

Kyle Knoepfel wrote:

We see no problem in creating the softlinks--in addition to cc, we would also provide the c++ and f95 softlinks.

However, we prefer to not export the environment variables that you request: doing so would adjust the default behavior of cmake and possibly other utilities (e.g. user-written make files). If you would like to argue for that aspect of this feature request, please bring it up at a stakeholders' meeting.

Thanks Kyle, not exporting the env vars is fine - thinking about it, users may want/need to set these themselves for testing/porting so best that they aren't set directly.

#3 Updated by Lynn Garren about 3 years ago

  • Status changed from Feedback to Assigned
  • Assignee set to Lynn Garren
  • Estimated time set to 2.00 h

#4 Updated by Lynn Garren almost 3 years ago

  • Status changed from Assigned to Resolved

Available with gcc 6.3

#5 Updated by Kyle Knoepfel almost 3 years ago

  • % Done changed from 0 to 100

#6 Updated by Lynn Garren over 2 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF