From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>, dhowells@redhat.com
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
ericvh@gmail.com, jaharkes@cs.cmu.edu, airlied@linux.ie
Subject: Re: linux-next: Tree for October 17 (build errors/warnings)
Date: Fri, 17 Oct 2008 18:01:03 -0400 [thread overview]
Message-ID: <1224280863.7517.2.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0810171346540.685@shark.he.net>
On Fri, 2008-10-17 at 13:56 -0700, Randy.Dunlap wrote:
> On Fri, 17 Oct 2008, Stephen Rothwell wrote:
>
> > 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.
>
> Since I don't have time to fix all of these, I'll just list a summary of
> today's randconfig build errors:
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> build-r9562.out:ksysfs.c:(.text+0x21463): undefined reference to `create_proc_profile'
> with CONFIG_PROC_FS=n, CONFIG_SYSFS=n
>
> build-r9567.out:linux-next-20081017/fs/nfsctl.c:45: error: implicit declaration of function 'current_cred'
This one doesn't have anything to do with my git tree. I'm assuming it
is related to the credentials patches from David Howells (cced).
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2008-10-17 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 8:40 linux-next: Tree for October 17 Stephen Rothwell
2008-10-17 9:30 ` Vegard Nossum
2008-10-17 16:18 ` Randy.Dunlap
2008-10-17 20:56 ` linux-next: Tree for October 17 (build errors/warnings) Randy.Dunlap
2008-10-17 22:01 ` Trond Myklebust [this message]
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=1224280863.7517.2.camel@localhost \
--to=trond.myklebust@netapp.com \
--cc=airlied@linux.ie \
--cc=dhowells@redhat.com \
--cc=ericvh@gmail.com \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).