all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Error when including openexr
Date: Thu, 1 Jun 2017 00:22:28 +0200	[thread overview]
Message-ID: <20170601002228.3978321a@scratchpost.org> (raw)
In-Reply-To: <592D8646.5040706@crazy-compilers.com>

Hi Hartmut,

On Tue, 30 May 2017 16:48:38 +0200
Hartmut Goebel <h.goebel@crazy-compilers.com> wrote:

> /gnu/store/…-openexr-2.2.0/include/OpenEXR/ImfInt64.h:44:24:
> fatal error: ImathInt64.h: No such file or directory
> 
> but file …-openexr-2.2.0/include/OpenEXR/ImathInt64.h exists.
> 
> I discovered that OpenEXR/ImfInt64.h contains
> 
> #include "ImathInt64.h"
> #include "ImfNamespace.h"
> 
> Maybe this should be "OpenEXR/ImathInt64.h" (same for the other)?

I think not.  cpp (the C preprocessor) has no notion of modules and what it does is just process #include "xx" relative to the directory of the file it currently reads (the one containing the "#include" directive), no matter how it went there.  (If it can't find it then it will fallback to the #include <xx> handler - but I think that's bad form).

(If you wanted to specify the "OpenEXR/" you'd usually put /gnu/store/…-openexr-2.2.0/include into the include path and include it like this in OpenEXR/ImfInt64.h : #include <OpenEXR/ImathInt64.h> with the <>)

Strange error message, though.

Is that gcc?  Which version?

  reply	other threads:[~2017-05-31 22:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30 14:48 Error when including openexr Hartmut Goebel
2017-05-31 22:22 ` Danny Milosavljevic [this message]
2017-06-01  8:07   ` julien lepiller
2017-06-01  9:34   ` Hartmut Goebel
2017-06-01 11:06 ` Andreas Enge
2017-06-03  8:03   ` Hartmut Goebel

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=20170601002228.3978321a@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.