public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: alaric@babcom.com
To: gcc-gnats@gcc.gnu.org
Subject: c/3675: gcc-3.0 fails to build linux-x-cygwin cross-compiler
Date: Fri, 13 Jul 2001 04:36:00 -0000 [thread overview]
Message-ID: <20010713113329.A954D209FD@babylon5.babcom.com> (raw)
>Number: 3675
>Category: c
>Synopsis: gcc-3.0 fails to build linux-x-cygwin cross-compiler
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Jul 13 04:36:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Mystic Zen Biker Twigboy
>Release: 3.0
>Organization:
Babylon Communications
>Environment:
System: Linux babylon5 2.4.6-ac2 #2 Sat Jul 7 18:23:45 PDT 2001 i586 unknown
Architecture: i586
host: i586-pc-linux-gnu
build: i586-pc-linux-gnu
target: i586-pc-linux-gnu
configured with: ../configure --prefix=/usr --with-gnu-as --with-gnu-ld --enable-shared
>Description:
gcc-3.0 will not build an i686-pc-linux-gnulibc2.1-x-i686-pc-cygwin
cross-compiler because FILE is not properly defined in
gcc-3.0/gcc/config/i386/cygwin.h, because __need_FILE is not defined
before including stdio.h.
>How-To-Repeat:
>Fix:
(ignore the timestamps, I fixed first then generated the patch)
*** gcc-3.0/gcc/config/i386/cygwin.h.orig Fri Jul 13 04:25:46 2001
--- gcc-3.0/gcc/config/i386/cygwin.h Fri Jul 13 04:22:31 2001
***************
*** 26,31 ****
--- 26,32 ----
#define SDB_DEBUGGING_INFO
#define PREFERRED_DEBUGGING_TYPE DBX_DEBUG
+ #define __need_FILE
#include <stdio.h> /* Required for FILE use below */
#include "i386/gas.h"
#include "dbxcoff.h"
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-07-13 4:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 4:36 alaric [this message]
2001-07-13 4:46 Phil Stracchino
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=20010713113329.A954D209FD@babylon5.babcom.com \
--to=alaric@babcom.com \
--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).