Project

General

Profile

Bug #1110

Cray builds break if explicitly passed compilers

Added by Sam White almost 3 years ago. Updated over 2 years ago.

Status:
Merged
Priority:
Normal
Category:
Build & Test Automation
Target version:
Start date:
06/22/2016
Due date:
% Done:

0%


Description

On most builds, we ask users to pass particular compiler options to ./build. On Cray systems, we want users to use the module files to set CC to to the compiler of their choice, then build. Right now, the build will fail if a user explicitly asks for a compiler even if they load that PrgEnv beforehand. This is inconsistent and confusing.

Proposed fix: the conv-mach files for different compilers should be empty for Cray systems, except they should test that the user has actually loaded the correct compiler if they ask for a specific one.

History

#1 Updated by Phil Miller almost 3 years ago

  • Category set to Build & Test Automation

#2 Updated by Seonmyeong Bak over 2 years ago

  • Status changed from New to Upstream

#3 Updated by Seonmyeong Bak over 2 years ago

  • Status changed from Upstream to Feedback

#4 Updated by Sam White over 2 years ago

  • Status changed from Feedback to Merged
  • % Done changed from 0 to 100
  • translation missing: en.field_closed_date set to 2016-08-04 14:00:09.199647

#5 Updated by Sam White over 2 years ago

  • Status changed from Merged to In Progress
  • % Done changed from 100 to 0
  • translation missing: en.field_closed_date deleted (2016-08-04 14:00:09.199647)

#7 Updated by Seonmyeong Bak over 2 years ago

  • Status changed from In Progress to Merged
  • translation missing: en.field_closed_date set to 2016-08-15 14:51:05.138631

#8 Updated by Phil Miller over 2 years ago

  • Target version changed from 6.8.0 to 6.8.0-beta1

Also available in: Atom PDF