From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Artem.Bityutskiy@nokia.com
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dmitry Pervushin <dpervushin@embeddedalley.com>
Subject: Re: linux-next: ubi tree build failure
Date: Fri, 5 Jun 2009 10:58:42 +1000 [thread overview]
Message-ID: <20090605105842.de948d0b.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4A265DF6.3070602@nokia.com>
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
Hi Artem,
On Wed, 03 Jun 2009 14:26:46 +0300 Artem Bityutskiy <Artem.Bityutskiy@nokia.com> wrote:
>
> Stephen Rothwell wrote:
> > Today's linux-next build (powerpc ppc44x_defconfig) failed like this:
> >
> > drivers/mtd/ubi/gluebi.c: In function 'gluebi_get_device':
> > drivers/mtd/ubi/gluebi.c:126: error: implicit declaration of function 'IS_ERR'
> > drivers/mtd/ubi/gluebi.c:129: error: implicit declaration of function 'PTR_ERR'
>
> It is strange that I do not see these errors on my x86_86
The above was a build for a 32 bit powerpc platform. This is an instance
of a general issue when an API is used without explicitly including the
header files that define the API. The needed header file may be included
by some convoluted path that depends on the architecture being built or
even the particular configuration.
> Any suggestions what I could do to reproduce the build issues?
> I'll try at least now to build this on x86 (32-bit).
Always directly include the header files for APIs you use ...
I see that this particular problem is now fixed, thanks.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-06-05 0:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 8:44 Stephen Rothwell
2009-06-03 8:46 ` Artem Bityutskiy
2009-06-03 11:26 ` Artem Bityutskiy
2009-06-03 12:55 ` Artem Bityutskiy
2009-06-03 13:05 ` dmitry pervushin
2009-06-03 13:07 ` Artem Bityutskiy
2009-06-05 0:58 ` Stephen Rothwell [this message]
2009-06-05 5:54 ` Artem Bityutskiy
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=20090605105842.de948d0b.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Artem.Bityutskiy@nokia.com \
--cc=dpervushin@embeddedalley.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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
all inboxes | Powered by JetHome®