public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/34422] Bootstrap error with --enable-fixed-point (configure should reject --enable-fixed-point on platforms that don't support it)
Date: Wed, 25 May 2022 02:15:30 +0000	[thread overview]
Message-ID: <bug-34422-4-VgLddBaSBu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-34422-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34422

--- Comment #10 from Eric Gallager <egallager at gcc dot gnu.org> ---
Current code is like this:

# Enable C extension for fixed-point arithmetic.
AC_ARG_ENABLE(fixed-point,
[AS_HELP_STRING([--enable-fixed-point],
                [enable fixed-point arithmetic extension to C])],
[],
[
  case $target in
    arm*)
      enable_fixed_point=yes
      ;;

    mips*-*-*)
      enable_fixed_point=yes
      ;;
    loongarch*-*-*)
      enable_fixed_point=yes
      ;;
    *)
      AC_MSG_WARN([fixed-point is not supported for this target, ignored])
      enable_fixed_point=no
      ;;
  esac
])
AC_SUBST(enable_fixed_point)

Let's check the documentation for AC_ARG_ENABLE:
https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.71/html_node/Package-Options.html

So, argument 3 is used if the flag is given, and argument 4 is used when the
flag is *not* given... so when it says "ignored" in the warning, there's
nothing being ignored, because the flag wasn't actually given... perhaps the
3rd and 4th arguments just need to be swapped?

  parent reply	other threads:[~2022-05-25  2:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-34422-4@http.gcc.gnu.org/bugzilla/>
2015-06-10 18:12 ` [Bug target/34422] Bootstrap error with --enable-fixed-point egall at gwmail dot gwu.edu
2020-11-20 22:43 ` egallager at gcc dot gnu.org
2022-05-24 15:07 ` [Bug target/34422] Bootstrap error with --enable-fixed-point (configure should reject --enable-fixed-point on platforms that don't support it) egallager at gcc dot gnu.org
2022-05-24 15:19 ` egallager at gcc dot gnu.org
2022-05-25  1:57 ` egallager at gcc dot gnu.org
2022-05-25  2:15 ` egallager at gcc dot gnu.org [this message]
2022-06-14 19:52 ` egallager at gcc dot gnu.org
2022-07-07 23:22 ` egallager at gcc dot gnu.org
2023-08-25 13:24 ` egallager at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-34422-4-VgLddBaSBu@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).