public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: corsepiu@faw.uni-ulm.de To: gcc-gnats@gcc.gnu.org Cc: joel@oarcorp.com Subject: other/10533: include-path broken for cross-gccs (PREFIX_INCLUDE_DIR) Date: Tue, 29 Apr 2003 01:36:00 -0000 [thread overview] Message-ID: <20030429013542.16654.qmail@sources.redhat.com> (raw) >Number: 10533 >Category: other >Synopsis: include-path broken for cross-gccs (PREFIX_INCLUDE_DIR) >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Apr 29 01:36:01 UTC 2003 >Closed-Date: >Last-Modified: >Originator: corsepiu@faw.uni-ulm.de >Release: gcc-3.2.x, gcc-3.3, gcc-3.4 >Organization: >Environment: Any. >Description: Any cross-gcc has $prefix/include before $prefix/<target>/include and $prefix/lib/gcc-lib/<target>/<version>/include in its include-path. This is not correct, because $prefix/include for cross-gccs contains host-headers, not target-headers, like it does for native gccs and therefore bogusly pulls-in host headers. >How-To-Repeat: Build a cross-gcc and examine the include-path Example: touch tmp.c i386-rtems-gcc -v -o tmp.o -c tmp.c gcc version 3.2.2 (OAR Corporation gcc-3.2.2-20030425/newlib-1.11.0-20030416a-0_rc_10) /opt/rtems/lib/gcc-lib/i386-rtems/3.2.2/cc1 -lang-c -v -D__GNUC__=3 -D__GNUC_MINOR__=2 -D__GNUC_PATCHLEVEL__=2 -D__GXX_ABI_VERSION=102 -D__rtems__ -D__ELF__ -D__i386__ -D__USE_INIT_FINI__ -D__rtems__ -D__ELF__ -D__i386__ -D__USE_INIT_FINI__ -Asystem=rtems -D__NO_INLINE__ -D__STDC_HOSTED__=1 -Acpu=i386 -Amachine=i386 -Di386 -D__i386 -D__i386__ -D__tune_i386__ tmp.c -quiet -dumpbase tmp.c -version -o /tmp/cc66lQPD.s GNU CPP version 3.2.2 (OAR Corporation gcc-3.2.2-20030425/newlib-1.11.0-20030416a-0_rc_10) (cpplib) (i386 bare ELF target) GNU C version 3.2.2 (OAR Corporation gcc-3.2.2-20030425/newlib-1.11.0-20030416a-0_rc_10) (i386-rtems) compiled by GNU C version 3.2.2 20030313 (Red Hat Linux 3.2.2-10). ignoring nonexistent directory "/opt/rtems/i386-rtems/sys-include" #include "..." search starts here: #include <...> search starts here: /opt/rtems/include /opt/rtems/lib/gcc-lib/i386-rtems/3.2.2/include /opt/rtems/i386-rtems/include End of search list. >Fix: The cause of this seems to be PREFIX_INCLUDE_DIR in gcc/configure.in. The patch in the attachment works around this issue by #undef'ing PREFIX_INCLUDE_DIR in cppdefaults.h for cross-compilation. >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="gcc-3.2.2-prefix-include-dir.diff" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="gcc-3.2.2-prefix-include-dir.diff" LS0tIC91c3IvbG9jYWwvc3JjL3BhY2thZ2VzL2djYy9zdWJ2ZXJzaW9ucy9nY2MtMy4yLjIvZ2Nj L2NwcGRlZmF1bHQuaAkyMDAxLTEwLTE0IDA5OjM1OjA3LjAwMDAwMDAwMCArMDIwMAorKysgZ2Nj LTMuMi4yL2djYy9jcHBkZWZhdWx0LmgJMjAwMy0wNC0yOCAyMzo1Mzo0OC4wMDAwMDAwMDAgKzAy MDAKQEAgLTM4LDYgKzM4LDcgQEAKICN1bmRlZiBMT0NBTF9JTkNMVURFX0RJUgogI3VuZGVmIFNZ U1RFTV9JTkNMVURFX0RJUgogI3VuZGVmIFNUQU5EQVJEX0lOQ0xVREVfRElSCisjdW5kZWYgUFJF RklYX0lOQ0xVREVfRElSCiAjZWxzZQogI3VuZGVmIENST1NTX0lOQ0xVREVfRElSCiAjZW5kaWYK
next reply other threads:[~2003-04-29 1:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-29 1:36 corsepiu [this message] 2003-04-29 14:07 bangerth
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=20030429013542.16654.qmail@sources.redhat.com \ --to=corsepiu@faw.uni-ulm.de \ --cc=gcc-gnats@gcc.gnu.org \ --cc=joel@oarcorp.com \ /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).