Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
darshan
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 71
    • Issues 71
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • darshan
  • darshan
  • Issues
  • #259

Closed
Open
Opened Jul 18, 2019 by Glenn K. Lockwood@glock
  • Report abuse
  • New issue
Report abuse New issue

autoconf should require GCC unless explicitly overridden

Darshan should always be built with GCC on Linux since it provides the most portability when linked against other applications. For users who know what they are doing and want to compile with a non-GCC compiler, there should be an explicit --without-gcc (or something) configure option that allows this behavior.

Looking around the Internet, it looks like the solution would be something like

#if defined(__GNUC__) && !defined(__clang__)

because both GCC and clang expose __GNUC__. Might want to check the common HPC compilers (Intel, PGI, Cray) to ensure that they aren't also flying a false flag like this.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: darshan/darshan#259