public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "v13 at it dot teithe dot gr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug pch/13675] #including a precompiled header more than once in the same unit fails Date: Sat, 24 Apr 2004 20:45:00 -0000 [thread overview] Message-ID: <20040424190909.29605.qmail@sources.redhat.com> (raw) In-Reply-To: <20040114031017.13675.jbrandmeyer@earthlink.net> ------- Additional Comments From v13 at it dot teithe dot gr 2004-04-24 19:09 ------- This is a way to reproduce it: hell:/tmp/2$ cat a.h #define A "koko" hell:/tmp/2$ cat b.h #include "a.h" #define C B hell:/tmp/2$ cat c.h #include "a.h" #include "b.h" #define D B hell:/tmp/2$ gcc a.h -o a.h.gch hell:/tmp/2$ gcc b.h -o b.h.gch hell:/tmp/2$ gcc c.h -o c.h.gch In file included from c.h:2: b.h:1:15: calling fdopen: Bad file descriptor hell:/tmp/2$ g++ a.h -o a.h.gch hell:/tmp/2$ g++ b.h -o b.h.gch hell:/tmp/2$ g++ c.h -o c.h.gch In file included from c.h:2: b.h:1:15: calling fdopen: Bad file descriptor But if we change c.h to: hell:/tmp/2$ cat c.h #include "b.h" #include "a.h" #define D B It works... So this happens when compiling header C which includes header B and A, and header B includes header A too, but only if header A is included in C before B. :) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13675
next prev parent reply other threads:[~2004-04-24 19:09 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-14 3:10 [Bug pch/13675] New: " jbrandmeyer at earthlink dot net 2004-01-14 12:29 ` [Bug pch/13675] " rwgk at yahoo dot com 2004-01-15 2:00 ` geoffk at gcc dot gnu dot org 2004-04-17 0:43 ` geoffk at gcc dot gnu dot org 2004-04-17 5:13 ` geoffk at gcc dot gnu dot org 2004-04-17 5:22 ` jbrandmeyer at earthlink dot net 2004-04-17 9:29 ` geoffk at gcc dot gnu dot org 2004-04-17 10:41 ` geoffk at gcc dot gnu dot org 2004-04-17 12:40 ` geoffk at gcc dot gnu dot org 2004-04-24 19:09 ` pinskia at gcc dot gnu dot org 2004-04-24 20:45 ` v13 at it dot teithe dot gr [this message] 2004-06-03 3:55 ` pegasus at ifdo dot pugmarks dot com 2004-06-25 22:02 ` geoffk at gcc dot gnu dot org 2005-09-22 10:54 ` a dot darovskikh at compassplus dot ru 2005-09-23 12:45 ` pinskia at gcc dot gnu dot org [not found] <bug-13675-6060@http.gcc.gnu.org/bugzilla/> 2006-04-01 23:19 ` rupert dot swarbrick at lineone dot net 2007-01-01 23:53 ` tim at klingt dot org 2007-05-17 23:06 ` tim at klingt dot org 2007-11-27 3:06 ` l dot bermes at eurokey dot de 2008-04-01 10:59 ` jakub at gcc dot gnu dot org 2008-10-17 20:20 ` jakub at gcc dot gnu dot org 2008-11-03 22:16 ` pinskia at gcc dot gnu dot org 2009-05-27 10:56 ` gafunchal at gmail dot com 2009-05-27 14:35 ` gafunchal at gmail dot com [not found] <bug-13675-4@http.gcc.gnu.org/bugzilla/> 2014-02-16 13:18 ` jackie.rosen at hushmail dot com
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=20040424190909.29605.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: 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).