From: Daniel Gollub <daniel.gollub@t-online.de>
To: Danny Al-Gaaf <danny.al-gaaf@bisect.de>
Cc: Jens Axboe <axboe@kernel.dk>, fio@vger.kernel.org
Subject: Re: [PATCH] crc/test.c: fix include of time.h
Date: Thu, 1 May 2014 10:05:40 +0200 [thread overview]
Message-ID: <20140501100540.6f9e18c0@marvin> (raw)
In-Reply-To: <53617267.8070909@bisect.de>
On Thu, 01 May 2014 00:00:07 +0200, Danny Al-Gaaf wrote:
> Am 30.04.2014 23:00, schrieb Jens Axboe:
> > On 04/30/2014 12:48 PM, Danny Al-Gaaf wrote:
> >> Replace include of time.h with renamed fio_time.h to fix build.
> >
> > Thanks Danny, applied. Mine still builds fine, for some odd
> > reason... But it of course needs fixing.
> >
>
> It seems it was the same strange issue for Daniel.
In my case (Ubuntu) the multi-arch packaging of glibc caused this:
[...]
25441 open("crc/../gettime.h", O_RDONLY|O_NOCTTY) = 4
25441 open("crc/../time.h", O_RDONLY|O_NOCTTY) = -1 ENOENT (No such file or directory)
25441 open("/usr/lib/gcc/x86_64-linux-gnu/4.7/include/../time.h", O_RDONLY|O_NOCTTY) = -1 ENOENT (No such file or directory)
25441 open("/usr/local/include/../time.h", O_RDONLY|O_NOCTTY) = -1 ENOENT (No such file or directory)
25441 open("/usr/lib/gcc/x86_64-linux-gnu/4.7/include-fixed/../time.h", O_RDONLY|O_NOCTTY) = -1 ENOENT (No such file or directory)
25441 open("/usr/include/x86_64-linux-gnu/../time.h", O_RDONLY|O_NOCTTY) = 4
[...]
I guess the same is true for all Debian-based distros doing multi-arch packaging like this.
Thanks Danny for finding this!
Best Regards
Daniel
prev parent reply other threads:[~2014-05-01 8:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 18:48 [PATCH] crc/test.c: fix include of time.h Danny Al-Gaaf
2014-04-30 21:00 ` Jens Axboe
2014-04-30 22:00 ` Danny Al-Gaaf
2014-05-01 8:05 ` Daniel Gollub [this message]
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=20140501100540.6f9e18c0@marvin \
--to=daniel.gollub@t-online.de \
--cc=axboe@kernel.dk \
--cc=danny.al-gaaf@bisect.de \
--cc=fio@vger.kernel.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: 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