public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: gni@gecko.de To: gcc-gnats@gcc.gnu.org Subject: other/10240: Don't use XCFLAGS for HOST_CFLAGS in gcc/Makefile.in Date: Thu, 27 Mar 2003 11:12:00 -0000 [thread overview] Message-ID: <200303271049.h2RAnbFv063022@lorien.int.gecko.de> (raw) >Number: 10240 >Category: other >Synopsis: HOST_CFLAGS in gcc/Makefile.in shouldn't include XCFLAGS >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Mar 27 10:56:01 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Gunther Nikl >Release: 3.3 20030303 (prerelease) >Organization: >Environment: build: i386-unknown-freebsd4.8 host: m68k-unknown-amigaos target: m68k-unknown-amigaos configured with: ../gcc-20030303-gg/configure --enable-languages=c --build=i386-unknown-freebsd4.8 --host=m68k-amigaos >Description: $(HOST_CFLAGS) of gcc/Makefile.in contains $(XCFLAGS) which might be set to something not suitable for the build machine. >How-To-Repeat: Add $(XCFLAGS) with an unsupported option for the build machine to a x-<target> fragment and configure with --build and --host. >Fix: Remove $(XCFLAGS) from $(HOST_CFLAGS) in gcc/Makefile.in >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-03-27 10:56 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200303271049.h2RAnbFv063022@lorien.int.gecko.de \ --to=gni@gecko.de \ --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: linkBe 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).