Configure errors

Simon Peyton Jones simon.peytonjones at gmail.com
Mon Aug 7 10:11:54 UTC 2023


But the other tests look like

checking for gnutar... no
checking for gtar... no
checking for tar... /usr/bin/tar
checking for gpatch... no
checking for patch... /usr/bin/patch
checking for autoreconf... /usr/bin/autoreconf

Can't you say

checking for -Qunused-arguments... no

You can explain this to me, now, and that helps me, today.  But I'm trying
to save you from having to explain it to many future GHC devs, and/or save
them time in hunting for answers to the same question.

No rush

Simon

On Mon, 7 Aug 2023 at 11:07, Rodrigo Mesquita <rodrigo.m.mesquita at gmail.com>
wrote:

> The trace is akin to the configure trace — it shows invocations of the
> toolchain in trying to determine properties of said toolchain e.g. which
> flags are supported.
>
> For example
>
>   checking for -Qunused-arguments support...
>   Entering: checking for -Qunused-arguments support
>     Execute: /usr/bin/gcc -Qunused-arguments -c -o /tmp/tmp0/test.o
> /tmp/tmp0/test.o.c
>     Command failed: /usr/bin/gcc -Qunused-arguments -c -o /tmp/tmp0/test.o
> /tmp/tmp0/test.o.c
> Exited with code 1
>
>   found for -Qunused-arguments support: Cc {ccProgram = Program {prgPath =
> "/usr/bin/gcc", prgFlags = []}}
>
>
> Is the trace of invoking the C compiler with -Qunused-arguments, checking
> whether the C compiler supports such an option.
> That command exited with code 1 likely because the compiler doesn’t indeed
> support -Qunused-arguments.
> That’s fine, it means we won’t pass -Qunused-arguments to your C compiler.
>
> Rodrigo
>
> On 7 Aug 2023, at 10:50, Simon Peyton Jones <simon.peytonjones at gmail.com>
> wrote:
>
> Rodrigo
>
> I'm getting lots of errors from ./configure, see below.
>
> Seems to be something to do with your toolchain stuff?  I'm lost.  Should
> I worry? If not, could they be made to look less alarming somehow?
>
> Simon
>
> Entering: checking for C compiler
>   checking for -Qunused-arguments support...
>   Entering: checking for -Qunused-arguments support
>     Execute: /usr/bin/gcc -Qunused-arguments -c -o /tmp/tmp0/test.o
> /tmp/tmp0/test.o.c
>     Command failed: /usr/bin/gcc -Qunused-arguments -c -o /tmp/tmp0/test.o
> /tmp/tmp0/test.o.c
> Exited with code 1
>
>   found for -Qunused-arguments support: Cc {ccProgram = Program {prgPath =
> "/usr/bin/gcc", prgFlags = []}}
>   checking whether Cc supports --target...
>   Entering: checking whether Cc supports --target
>     Execute: /usr/bin/gcc -Werror --target=x86_64-unknown-linux -c -o
> /tmp/tmp0/test.o /tmp/tmp0/test.o.c
>     Command failed: /usr/bin/gcc -Werror --target=x86_64-unknown-linux -c
> -o /tmp/tmp0/test.o /tmp/tmp0/test.o.c
> Exited with code 1
>
>   found whether Cc supports --target: Cc {ccProgram = Program {prgPath =
> "/usr/bin/gcc", prgFlags = []}}
>   checking whether Cc works...
>   Entering: checking whether Cc works
>     Execute: /usr/bin/gcc -c -o /tmp/tmp0/test.o /tmp/tmp0/test.o.c
>   found whether Cc works: ()
>   checking for C99 support...
>   Entering: checking for C99 support
>     Execute: /usr/bin/gcc -c -o /tmp/tmp0/test.o /tmp/tmp0/test.o.c
>   found for C99 support: ()
>   checking whether cc supports extra via-c flags...
>   Entering: checking whether cc supports extra via-c flags
>     Execute: /usr/bin/gcc -c -fwrapv -fno-builtin -Werror -x c -o
> /tmp/tmp0/test.o /tmp/tmp0/test.c
>   found whether cc supports extra via-c flags: ()
> found for C compiler: Cc {ccProgram = Program {prgPath = "/usr/bin/gcc",
> prgFlags = []}}
> checking for C++ compiler...
> Entering: checking for C++ compiler
>   x86_64-unknown-linux-g++ not found in search path
>   x86_64-unknown-linux-clang++ not found in search path
>   x86_64-unknown-linux-c++ not found in search path
>   checking whether C++ supports --target...
>   Entering: checking whether C++ supports --target
>     Execute: /usr/bin/g++ -Werror --target=x86_64-unknown-linux -c -o
> /tmp/tmp0/test.o /tmp/tmp0/test.o.cpp
>     Command failed: /usr/bin/g++ -Werror --target=x86_64-unknown-linux -c
> -o /tmp/tmp0/test.o /tmp/tmp0/test.o.cpp
> Exited with code 1
>
>   found whether C++ supports --target: Cxx {cxxProgram = Program {prgPath
> = "/usr/bin/g++", prgFlags = []}}
>   Execute: /usr/bin/g++ -c -o /tmp/tmp0/test.o /tmp/tmp0/test.o.cpp
> found for C++ compiler: Cxx {cxxProgram = Program {prgPath =
> "/usr/bin/g++", prgFlags = []}}
> checking for C preprocessor...
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20230807/2f6dc0d4/attachment.html>


More information about the ghc-devs mailing list