public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bradley-gnu@bradley.lcs.mit.edu
To: gcc-gnats@gcc.gnu.org
Subject: driver/9822: The "%c" spec option produces: gcc: spec failure: unrecognized spec option 'c'
Date: Mon, 24 Feb 2003 06:36:00 -0000	[thread overview]
Message-ID: <20030224062723.994.qmail@sources.redhat.com> (raw)


>Number:         9822
>Category:       driver
>Synopsis:       The "%c" spec option produces: gcc: spec failure: unrecognized spec option 'c'
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Feb 24 06:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     bradley-gnu@bradley.lcs.mit.edu
>Release:        gcc-3.2.1
>Organization:
>Environment:

>Description:
I tried to write a spec file that used the %c option, but it is no longer accepted by the driver.  The error is printed by line 5234 of gcc.c.

The gcc.info documentation says that %c is accepted, however:
> `%c'
>     Process the `signed_char' spec.  This is intended to be used to
>     tell cpp whether a char is signed.  It typically has the
>     definition:
>          %{funsigned-char:-D__CHAR_UNSIGNED__}

This is probably a documentation bug, rather than a code bug.

The documentation on the spec files seems quite out-of-date.
For example, I cannot figure out, from the documentation, what does this entry mean in the spec file.
 %{fsigned-char&unsigned-char}


>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-02-24  6:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24  6:36 bradley-gnu [this message]
2003-02-24  7:16 Neil Booth
2003-03-14  2:23 bangerth

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=20030224062723.994.qmail@sources.redhat.com \
    --to=bradley-gnu@bradley.lcs.mit.edu \
    --cc=gcc-gnats@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).