From: Mike Frysinger <vapier@gentoo.org>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH 1/2 v2] rewrite build system to avoid recursion
Date: Sat, 25 Jun 2011 13:08:10 -0400 [thread overview]
Message-ID: <BANLkTin+Or+320Uz5bSj26yFJE2BZgO2dA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinJkfNpJ-13yTwpx9u-FaX1TKScuw@mail.gmail.com>
On Sat, Jun 25, 2011 at 03:48, Mike Frysinger wrote:
> On Sat, Jun 25, 2011 at 03:13, Artem Bityutskiy wrote:
>> CC ubi-utils/ubinize.o
>> In file included from ubi-utils/ubinize.c:38:0:
>> ./ubi-utils/include/libiniparser.h:35:24: fatal error: dictionary.h: No
>> such file or directory
>> compilation terminated.
>> make: *** [/home/dedekind/git/mtd-utils/ubi-utils/ubinize.o] Error 1
>
> weird ... i'm not seeing that. i'll double check my system in the
> morning to see what's going on.
i had /usr/include/dictionary.h which provided the same thing
so how to solve ... i dont quite understand the file layout in
ubi-utils. why isnt dictionary.h in the include/ subdir ? after all,
that's where the include is coming from:
ubi-utils/include/libiniparser.h.
-mike
next prev parent reply other threads:[~2011-06-25 17:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-25 6:30 [PATCH] rewrite build system to avoid recursion Mike Frysinger
2011-06-25 6:32 ` Mike Frysinger
2011-06-25 6:52 ` [PATCH 1/2 v2] " Mike Frysinger
2011-06-25 6:52 ` [PATCH 2/2] autogenerate version.h from build system Mike Frysinger
2011-06-25 7:13 ` [PATCH 1/2 v2] rewrite build system to avoid recursion Artem Bityutskiy
2011-06-25 7:48 ` Mike Frysinger
2011-06-25 17:08 ` Mike Frysinger [this message]
2011-06-25 17:20 ` [PATCH 1/2 v3] " Mike Frysinger
2011-06-25 17:20 ` [PATCH 2/2 v2] autogenerate version.h from build system Mike Frysinger
2011-06-27 6:11 ` [PATCH 1/2 v3] rewrite build system to avoid recursion Artem Bityutskiy
2011-06-27 16:53 ` Brian Norris
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=BANLkTin+Or+320Uz5bSj26yFJE2BZgO2dA@mail.gmail.com \
--to=vapier@gentoo.org \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.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