public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Per Bothner <bothner@bothner.com>
To: gcc-gnats@gcc.gnu.org
Subject: preprocessor/3104: pre-processor does not search $includedir
Date: Sat, 09 Jun 2001 18:16:00 -0000 [thread overview]
Message-ID: <200106092313.f59NDZs07667@eureka.bothner.com> (raw)
>Number: 3104
>Category: preprocessor
>Synopsis: pre-processor does not search $includedir
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sat Jun 09 18:16:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Per Bothner
>Release: 3.0 20010608 (prerelease)
>Organization:
Brainfood Inc
>Environment:
System: Linux eureka.bothner.com 2.4.2-2 #1 Sun Apr 8 20:41:30 EDT 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: /home/bothner/GNU/gcc3/configure --enable-threads --prefix=/home/bothner/GNU/install-gcc3 --enable-languages=C++,java : (reconfigured)
>Description:
The pre-processor by default does not search $includedir aka
$prefix/include. It does search /usr/include and /usr/local/include,
so this is only for problem if gcc is configured with a non-default
--prefix - which many of us do!
Thia probably violates the GNU coding standards, which say that packages
should install include files in $includedir. One package which does this
is libjava. Thus using gcj's CNI does not work (with default options)
if you use a non-standard --prefix.
>How-To-Repeat:
>Fix:
Fix either cppdefault.c or the Makefile.in.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-06-09 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-09 18:16 Per Bothner [this message]
2001-06-10 3:17 neil
2001-06-10 3:52 neil
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=200106092313.f59NDZs07667@eureka.bothner.com \
--to=bothner@bothner.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).