public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: fonseca@mip.sdu.dk
To: gcc-gnats@gcc.gnu.org
Subject: c/4157: space missing in gcc-3.0.1/gcc/config/i386/cygwin.h
Date: Tue, 28 Aug 2001 08:36:00 -0000	[thread overview]
Message-ID: <20010828153113.12048.qmail@sourceware.cygnus.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]

>Number:         4157
>Category:       c
>Synopsis:       space missing in gcc-3.0.1/gcc/config/i386/cygwin.h
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 28 08:36:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     René Fonseca
>Release:        gcc version 3.0.1
>Organization:
>Environment:

>Description:
A missing space in the source file "gcc-3.0.1/gcc/config/i386/cygwin.h" prevents compilation with the option "-mno-cygwin". The missing space results in an invalid spec string.

A compilation like "gcc -mno-cygwin mysource.c" results in:
cc1.exe: Output filename specified twice

Sorry, no full dump with option "-v". Looks very bad in this gnatsweb-window.
>How-To-Repeat:

>Fix:
Here you have the diff output of the before and after source file:

83c83
<                      "-isystem /usr/local/include/mingw" \
---
>                      "-isystem /usr/local/include/mingw " \
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-08-28  8:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-28  8:36 fonseca [this message]
2001-10-13 22:34 rodrigc

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=20010828153113.12048.qmail@sourceware.cygnus.com \
    --to=fonseca@mip.sdu.dk \
    --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).