public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ilgis@num.uni-sb.de To: gcc-gnats@gcc.gnu.org Cc: info@ilghiz.com Subject: preprocessor/10014: Problems with "#include __BASE_FILE__" in different dirrectories Date: Mon, 10 Mar 2003 10:56:00 -0000 [thread overview] Message-ID: <20030310105444.17654.qmail@sources.redhat.com> (raw) >Number: 10014 >Category: preprocessor >Synopsis: Problems with "#include __BASE_FILE__" in different dirrectories >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Mon Mar 10 10:56:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: ilgis@num.uni-sb.de >Release: gcc-2.95.3, gcc-3.0, gcc-3.2 >Organization: >Environment: Linux Red Hat 7.1 and Linux Suse 8.0 >Description: Let's create a simple "test.c" file with only one line: /******************* begin test.c ********************/ #include "in.h" /******************* end test.c **********************/ and create this header file "in.h" as following: /******************* begin in.h **********************/ #ifndef SWSIZE #define SWSIZE 1 #include __BASE_FILE__ #undef SWSIZE #define SWSIZE 2 #endif #if ( SWSIZE == 1 ) // some special definitions #else // some special definitions #endif /********************** end in.h ********************/ if both files are in the same dirrectory then we can succesfully compile it with the following command: cc -c test.c but if "in.h" is, for example, in INCLUDE dirrectory, then cc -c -IINCLUDE test.c produces the following message: In file included from test.c:1: INCLUDE/in.h:3: test.c: No such file or directory It is possible to solve it by dirrective like: cc -c -IINCLUDE $(PWD)/test.c but it seems a little bit strange! >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-03-10 10:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-10 10:56 ilgis [this message] 2003-03-10 11:04 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=20030310105444.17654.qmail@sources.redhat.com \ --to=ilgis@num.uni-sb.de \ --cc=gcc-gnats@gcc.gnu.org \ --cc=info@ilghiz.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).