Skip to content
Snippets Groups Projects

configure script uses different CFLAGS from the actual build

    • Open Issue created by dobenour @trac-dobenour

    configure fails to set CFLAGS to the value that will actually be used. This can result in checks giving wrong results. I discovered this when working on D2996, where it led to a build failure using Clang.

    Note that -Werror cannot be used during most checks in configure, but is necessary for FP_CHECK_FLAG.

    Trac metadata
    Trac field Value
    Version 8.1
    Type Task
    TypeOfFailure OtherFailure
    Priority normal
    Resolution Unresolved
    Component Build System
    Test case
    Differential revisions
    BlockedBy
    Related
    Blocking
    CC
    Operating system
    Architecture
    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items 0

    • No child items are currently assigned. Use child items to break down this issue into smaller parts.

    Activity

    • dobenour changed weight to 5

      changed weight to 5

    • dobenour added Ttask Trac import labels

      added Ttask Trac import labels

    • rwbarton
      rwbarton @trac-rwbarton ·

      Could you be more specific? There are various sets of flags and even potentially multiple C compilers that will be used at different points during the build of GHC.

      And in the instance in D2996, it looks like the failure occurred while compiling the RTS; but -Werror was in effect only because this was part of a validate build. More generally the user can specify additional options for building the RTS via the make variable GhcRtsCcOpts, and we can't know the value of that variable at configure time.

    • Ben Gamari
      Ben Gamari @bgamari ·
      Maintainer

      The new Hadrian build system has been merged. Relabeling the tickets concerning the legacy make build system to prevent confusion.

      Trac metadata
      Trac field Value
      Component Build System → Build System (make)
    • jberryman
      jberryman @trac-jberryman ·

      I'm confused as to what CFLAGS is meant to do. If I do for instance:

      $ LD=gold CFLAGS="-time=/tmp/does_cflags_work" LDFLAGS="-time=/tmp/does_cflags_work.l" CC_STAGE0=gcc CC=gcc  ./configure
$ make

      I can see nothing is logged to either of those files during make (there are lines during configure).

      Yet fiddling with CFLAGS did seem to do something when doing CC=clang but I had too many balls in the air to look into it further...

    • trac-import added ghc build failure label

      added ghc build failure label

    • Ben Gamari added Pnormal label

      added Pnormal label

    • Rodrigo Mesquita mentioned in issue #24636

      mentioned in issue #24636

    Please register or sign in to reply