From: maximilian attems <max-U9r9yeDMy7A@public.gmane.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org,
Trond Myklebust <Trond.Myklebust@netapp.com>,
klibc@zytor.com
Subject: Re: nfs MNT include cleanup
Date: Tue, 18 Aug 2009 12:36:53 +0200 [thread overview]
Message-ID: <20090818103653.GB3954@stro.at> (raw)
In-Reply-To: <C7D2AC7D-48B2-4206-A6B1-3780FE7D51CE@oracle.com>
On Tue, 11 Aug 2009, Chuck Lever wrote:
> On Aug 11, 2009, at 6:44 AM, maximilian attems wrote:
> >2ad780978b7c0c3e7877949f098cbd06e7c73839 broke klibc build
> >MNTPROC_MNT and MNTPROC_UMNT no longer defined.
>=20
> I assume then that klibc is out of tree? I can't find it in my
> kernel repo.
sorry for late reply, indeed you'll find it here:
http://git.kernel.org/?p=3Dlibs/klibc/klibc.git;a=3Dsummary
=20
> >usr/kinit/nfsmount/mount.c: In function =E2=80=98mount_call=E2=80=99=
:
> >usr/kinit/nfsmount/mount.c:179: error: =E2=80=98MNTPROC_MNT=E2=80=99=
undeclared
> >(first use in this function)
> >usr/kinit/nfsmount/mount.c:179: error: (Each undeclared identifier
> >is reported only once
> >usr/kinit/nfsmount/mount.c:179: error: for each function it
> >appears in.)
> >usr/kinit/nfsmount/mount.c: In function =E2=80=98mount_v2=E2=80=99:
> >usr/kinit/nfsmount/mount.c:211: error: =E2=80=98MNTPROC_MNT=E2=80=99=
undeclared
> >(first use in this function)
> >usr/kinit/nfsmount/mount.c: In function =E2=80=98umount_v2=E2=80=99:
> >usr/kinit/nfsmount/mount.c:226: error: =E2=80=98MNTPROC_UMNT=E2=80=99=
undeclared
> >(first use in this function)
> >usr/kinit/nfsmount/mount.c: In function =E2=80=98mount_v3=E2=80=99:
> >usr/kinit/nfsmount/mount.c:232: error: =E2=80=98MNTPROC_MNT=E2=80=99=
undeclared
> >(first use in this function)
> >usr/kinit/nfsmount/mount.c: In function =E2=80=98umount_v3=E2=80=99:
> >usr/kinit/nfsmount/mount.c:251: error: =E2=80=98MNTPROC_UMNT=E2=80=99=
undeclared
> >(first use in this function)
> >make[4]: *** [usr/kinit/nfsmount/mount.o] Error 1
> >make[3]: *** [usr/kinit/nfsmount] Error 2
> >make[2]: *** [all] Error 2
> >make[1]: *** [klibc] Error 2
> >make[1]: Leaving directory `/home/maks/src/klibc-latest'
we might still define those for ourselve, let's see..
next prev parent reply other threads:[~2009-08-18 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 10:44 nfs MNT include cleanup maximilian attems
[not found] ` <20090811104418.GA6175-U9r9yeDMy7A@public.gmane.org>
2009-08-11 18:55 ` Chuck Lever
2009-08-18 10:36 ` maximilian attems [this message]
[not found] ` <20090818103653.GB3954-U9r9yeDMy7A@public.gmane.org>
2009-08-18 12:45 ` Chuck Lever
2009-08-18 12:44 ` maximilian attems
[not found] ` <20090818124406.GD13440-P4at2qFsAtP5lb2fJPEjcQ@public.gmane.org>
2009-08-18 13:19 ` Chuck Lever
2009-08-18 16:04 ` [klibc] " H. Peter Anvin
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=20090818103653.GB3954@stro.at \
--to=max-u9r9yedmy7a@public.gmane.org \
--cc=Trond.Myklebust@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=klibc@zytor.com \
--cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.