public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: zwlu@ucdavis.edu
To: gcc-gnats@gcc.gnu.org
Subject: c/3031: GCC_EXEC_PREFIX does not work properly on 2.95.3
Date: Fri, 01 Jun 2001 10:56:00 -0000	[thread overview]
Message-ID: <20010601175511.19049.qmail@sourceware.cygnus.com> (raw)

>Number:         3031
>Category:       c
>Synopsis:       GCC_EXEC_PREFIX does not work properly on 2.95.3
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jun 01 10:56:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     zwlu@ucdavis.edu
>Release:        gcc 2.95.3
>Organization:
>Environment:

Redhat Linux 7.1 system
>Description:
After setting GCC_EXEC_PREFIX=/usr/i386-glibc21-linux/lib/gcc-lib/
gcc 2.95.3 fails to use header files from
/usr/i386-glibc21-linux/include, it still uses /usr/include instead.

The library search path appears to be correct as reported by
gcc -print-search-dirs.
>How-To-Repeat:

>Fix:

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


                 reply	other threads:[~2001-06-01 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=20010601175511.19049.qmail@sourceware.cygnus.com \
    --to=zwlu@ucdavis.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).