public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: andreas@andreas-jung.com
To: gcc-gnats@gcc.gnu.org
Subject: c/2584: gcc omits /usr/local/include
Date: Wed, 18 Apr 2001 17:36:00 -0000 [thread overview]
Message-ID: <20010419002636.25404.qmail@sourceware.cygnus.com> (raw)
>Number: 2584
>Category: c
>Synopsis: gcc omits /usr/local/include
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Apr 18 17:36:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Andreas Jung
>Release: gcc-2.95.3
>Organization:
>Environment:
linux 2.4.3 i686
>Description:
gcc forgets to include files from its default path /usr/local/include.
This path is omited
yetix@/usr2/home/ajung(14)% gcc -v identd.c
Reading specs from /opt/gcc-2.95.3/lib/gcc-lib/i586-pc-linux-gnu/2.95.3/specs
gcc version 2.95.3 20010315 (release)
/opt/gcc-2.95.3/lib/gcc-lib/i586-pc-linux-gnu/2.95.3/cpp0 -lang-c -v -D__GNUC__=2 -D__GNUC_MINOR__=95 -D__ELF__ -Dunix -D__i386__ -Dlinux -D__ELF__ -D__unix__ -D__i386__ -D__linux__ -D__unix -D__linux -Asystem(posix) -Acpu(i386) -Amachine(i386) -Di386 -D__i386 -D__i386__ -Di586 -Dpentium -D__i586 -D__i586__ -D__pentium -D__pentium__ identd.c /tmp/ccM6IwrA.i
GNU CPP version 2.95.3 20010315 (release) (i386 Linux/ELF)
#include "..." search starts here:
#include <...> search starts here:
/opt/gcc-2.95.3/include
/opt/gcc-2.95.3/lib/gcc-lib/i586-pc-linux-gnu/2.95.3/../../../../i586-pc-linux-gnu/include
/opt/gcc-2.95.3/lib/gcc-lib/i586-pc-linux-gnu/2.95.3/include
/usr/include
End of search list.
...
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
reply other threads:[~2001-04-18 17:36 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=20010419002636.25404.qmail@sourceware.cygnus.com \
--to=andreas@andreas-jung.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).