public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alfred von Campe <alfred@von-campe.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Strange gcc #include behavior when compiling multiple source files at once
Date: Tue, 06 Dec 2011 14:39:00 -0000	[thread overview]
Message-ID: <6EADED68-C710-417C-A51B-33E1FD66A49E@von-campe.com> (raw)
In-Reply-To: <CAH6eHdSXxM+vLmZTvX1tdMSpQUgBa2uBSTAA8HOkQaTcC9+hDA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 835 bytes --]

On Dec 6, 2011, at 9:19, Jonathan Wakely wrote:

> The most basic step would be to add -v to the command line and inspect
> the output (it's not clear from your email if you've already done
> that.)

No, I had not.  I just did and can't quite decipher what (if anything) the
output is trying to tell me.  Would you (or someone else on this list) try
to take a stab at it?  I've attached the (slightly redacted) log file.  But
keep in mind that the init_frame_buffer.i file contains the contents of the
ipc_defines.h include file despite the compiler complaining about "No such
file or directory" as I mentioned in my original post.  Creating a symlink
from ../../../LPM/LPMcode/ipc_defines.h to ../../../LPM/share/ipc_defines.h
makes the compiler happy, even though both directories are specified with -I
on the command line.

Alfred


[-- Attachment #2: gcc.log.gz --]
[-- Type: application/x-gzip, Size: 2495 bytes --]

  reply	other threads:[~2011-12-06 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06 14:07 Alfred von Campe
2011-12-06 14:19 ` Jonathan Wakely
2011-12-06 14:39   ` Alfred von Campe [this message]
2011-12-08 15:03 ` Alfred von Campe

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=6EADED68-C710-417C-A51B-33E1FD66A49E@von-campe.com \
    --to=alfred@von-campe.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.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: 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).