public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: fcusack@fcusack.com To: gcc-gnats@gcc.gnu.org Subject: other/9056: configure always defines PREFIX_INCLUDE_DIR Date: Wed, 25 Dec 2002 00:16:00 -0000 [thread overview] Message-ID: <20021225080919.31980.qmail@sources.redhat.com> (raw) >Number: 9056 >Category: other >Synopsis: configure always defines PREFIX_INCLUDE_DIR >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Dec 25 00:16:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Frank Cusack >Release: 3.2.1 >Organization: >Environment: >Description: This bit from gcc/configure.in: if test "$prefix" != "/usr" && test "$prefix" != "/usr/local" ; then AC_DEFINE_UNQUOTED(PREFIX_INCLUDE_DIR, "$prefix/include") fi always includes $prefix/include. (The condition can never be false.) Also, why is this always set? This makes gcc unbuildable in my environment (including in $prefix/include requires linking against $prefix/lib, which I don't want). >How-To-Repeat: >Fix: if test "$prefix" == "/usr" || test "$prefix" == "/usr/local" ; then : else AC_DEFINE_UNQUOTED(PREFIX_INCLUDE_DIR, "$prefix/include") fi >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-12-25 8:16 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=20021225080919.31980.qmail@sources.redhat.com \ --to=fcusack@fcusack.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: 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).