From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Eric Van Hensbergen <ericvh@gmail.com>,
Ron Minnich <rminnich@sandia.gov>,
Latchesar Ionkov <lucho@ionkov.net>
Subject: Re: linux-next: Tree for October 17
Date: Fri, 17 Oct 2008 09:18:36 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0810170917200.685@shark.he.net> (raw)
In-Reply-To: <19f34abd0810170230s755aa0e4vea38c26e093e173c@mail.gmail.com>
On Fri, 17 Oct 2008, Vegard Nossum wrote:
> On Fri, Oct 17, 2008 at 10:40 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > Hi all,
> >
> > Today's tree will not build for powerpc allyesconfig (libc aborts the
> > link due to a free() problem), sparc(32) defconfig and probably some
> > other configurations.
>
> Hi, I ran into this with slightly modified fedora config:
>
> CC net/9p/protocol.o
> net/9p/protocol.c: In function 'p9pdu_finalize':
> net/9p/protocol.c:545: error: 'p9_debug_level' undeclared (first use
> in this function)
> net/9p/protocol.c:545: error: (Each undeclared identifier is reported only once
> net/9p/protocol.c:545: error: for each function it appears in.)
> net/9p/protocol.c:545: error: 'P9_DEBUG_PKT' undeclared (first use in
> this function)
> make[2]: *** [net/9p/protocol.o] Error 1
> make[1]: *** [net/9p] Error 2
> make: *** [net] Error 2
>
> ...and couldn't find it in the automatic build test results either. 9P
> maintainers Cced.
This build failure happened with 20081016 also.
There are plenty of randconfig build failures and not enough time
in the day to fix all of them before Stephen produces the next next.
--
~Randy
next prev parent reply other threads:[~2008-10-17 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 8:40 Stephen Rothwell
2008-10-17 9:30 ` Vegard Nossum
2008-10-17 16:18 ` Randy.Dunlap [this message]
2008-10-17 20:56 ` linux-next: Tree for October 17 (build errors/warnings) Randy.Dunlap
2008-10-17 22:01 ` Trond Myklebust
2008-10-18 2:23 ` David Howells
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=Pine.LNX.4.64.0810170917200.685@shark.he.net \
--to=rdunlap@xenotime.net \
--cc=ericvh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=rminnich@sandia.gov \
--cc=sfr@canb.auug.org.au \
--cc=vegard.nossum@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
all inboxes | Powered by JetHome®