public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Artur.Klauser@computer.org
To: gcc-gnats@gcc.gnu.org
Cc: Artur.Klauser@computer.org
Subject: bootstrap/4406: wrong include file search paths compiled into cc1
Date: Wed, 26 Sep 2001 16:46:00 -0000 [thread overview]
Message-ID: <200109262338.TAA22991@shlc0014.shr.intel.com> (raw)
>Number: 4406
>Category: bootstrap
>Synopsis: wrong include file search paths compiled into cc1
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: rejects-legal
>Submitter-Id: net
>Arrival-Date: Wed Sep 26 16:46:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:
>Release: 3.0.1
>Organization:
>Environment:
System: Linux shlc0014.shr.intel.com 2.2.17-14 #1 Thu May 17 13:37:40 PDT 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: /proj/vssad/local/src/g/gcc-3.0.1/configure --prefix=/proj/vssad/local/common --exec-prefix=/proj/vssad/local/i386_linux22 --with-gxx-include-dir=/proj/vssad/local/common/include/g++-v3 --enable-threads=posix
>Description:
When trying to configure GCC for multi-platform install (--prefix
different from --exec-prefix), the include search paths in (at least)
cc1 are misconfigured and point to non-existing directories.
Note 1: the installation of the include files is still in the correct places.
Note 2: I have only tested the C++ installation - other languages
might be affected.
>How-To-Repeat:
./configure --prefix=/proj/vssad/local/common --exec-prefix=/proj/vssad/local/i386_linux22
results in the following output of cc1 (note lines maked with *****:
-------------------------------------------------------------------------------
# /proj/vssad/local/i386_linux22/bin/g++ -MD -c -o x.o -O0 -g -v x.cpp
Reading specs from /proj/vssad/local/i386_linux22/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/specs
Configured with: /proj/vssad/local/src/g/gcc-3.0.1/configure --prefix=/proj/vssad/local/common --exec-prefix=/proj/vssad/local/i386_linux22 --enable-threads=posix
Thread model: posix
gcc version 3.0.1
/proj/vssad/local/i386_linux22/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/cc1plus -v -MM -MF x.d -MQ x.o -D__GNUC__=3 -D__GNUC_MINOR__=0 -D__GNUC_PATCHLEVEL__=1 -D__ELF__ -Dunix -Dlinux -D__ELF__ -D__unix__ -D__linux__ -D__unix -D__linux -Asystem=posix -D__NO_INLINE__ -D__STDC_HOSTED__=1 -D_GNU_SOURCE -Acpu=i386 -Amachine=i386 -Di386 -D__i386 -D__i386__ -D__tune_i686__ -D__tune_pentiumpro__ x.cpp -D__GNUG__=3 -D__GXX_DEPRECATED -D__EXCEPTIONS -D__GXX_ABI_VERSION=100 -quiet -dumpbase x.cpp -g -O0 -version -o /tmp/ccLWOnFB.s
GNU CPP version 3.0.1 (cpplib) (i386 Linux/ELF)
GNU C++ version 3.0.1 (i686-pc-linux-gnu)
compiled by GNU C version 3.0.1.
***** ignoring nonexistent directory "/include/g++-v3"
***** ignoring nonexistent directory "/include/g++-v3/i686-pc-linux-gnu"
***** ignoring nonexistent directory "/include/g++-v3/backward"
***** ignoring nonexistent directory "/proj/i686-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/local/include
/proj/vssad/local/i386_linux22/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/include
/usr/include
End of search list.
-------------------------------------------------------------------------------
Looking at cc1 reveals that the wrong include search paths have been
compiled in:
-------------------------------------------------------------------------------
### the problem seems to be that the compiled in path is cooked up wrong ###
Linux-14:~# strings /proj/vssad/local/i386_linux22/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/cc1 | grep include
[... some lines deleted ...]
/proj/vssad/local/i386_linux22/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/../../../../../../../../include/g++-v3
/proj/vssad/local/i386_linux22/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/../../../../../../../../include/g++-v3/i686-pc-linux-gnu
/proj/vssad/local/i386_linux22/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/../../../../../../../../include/g++-v3/backward
/usr/local/include
/proj/vssad/local/i386_linux22/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/include
/proj/vssad/local/i386_linux22/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/../../../../../../../i686-pc-linux-gnu/include
/usr/include
/proj/vssad/local/i386_linux22/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/include
-------------------------------------------------------------------------------
>Fix:
Workaround can be done with
--with-gxx-include-dir=/proj/vssad/local/common/include/g++-v3
A real fix would be required in the configure procedure or Makefile
that generates the paths to be compiled into cc1.
>Release-Note:
>Audit-Trail:
>Unformatted:
reply other threads:[~2001-09-26 16:46 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=200109262338.TAA22991@shlc0014.shr.intel.com \
--to=artur.klauser@computer.org \
--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).