Date: Sat, 22 Jun 2013 09:42:18 -0700 From: hiren panchasara <hiren.panchasara@gmail.com> To: "O. Hartmann" <ohartman@zedat.fu-berlin.de> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: revision 252095: kerenl fails to compile: nfs_clstate.c:5160:33: error: format specifies type 'long long' but the argument has type 'uint64_t' Message-ID: <CALCpEUG98BmK5Hh58xWPr4d39VgptpoTfsjnEj-1Phk5VM213g@mail.gmail.com> In-Reply-To: <20130622150856.5e6f9c90@thor.walstatt.dyndns.org> References: <20130622150856.5e6f9c90@thor.walstatt.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 22, 2013 6:09 AM, "O. Hartmann" <ohartman@zedat.fu-berlin.de> wrote: > > > Just for notice. > > The most recent sources fail to compile a kernel successfully: http://svnweb.freebsd.org/changeset/base/252074 This change is the culprit. Hiren > > > [...] > /usr/src/sys/fs/nfsclient/nfs_clstate.c:5160:33: error: format > specifies type 'long long' but the argument has type 'uint64_t' (aka > 'unsigned long') [-Werror,-Wformat] "lastbyte=%qd\n", error, > flp->nfsfl_off, len, ^~~~~~~~~~~~~~ > /usr/src/sys/fs/nfs/nfscl.h:74:11: note: expanded from macro > 'NFSCL_DEBUG' printf(__VA_ARGS__); \ > ^ > /usr/src/sys/fs/nfsclient/nfs_clstate.c:5160:49: error: format > specifies type 'long long' but the argument has type 'uint64_t' (aka > 'unsigned long') [-Werror,-Wformat] "lastbyte=%qd\n", error, > flp->nfsfl_off, len, ^~~ > /usr/src/sys/fs/nfs/nfscl.h:74:11: note: expanded from macro > 'NFSCL_DEBUG' printf(__VA_ARGS__); \ > ^ > /usr/src/sys/fs/nfsclient/nfs_clstate.c:5161:8: error: format specifies > type 'long long' but the argument has type 'uint64_t' (aka 'unsigned > long') [-Werror,-Wformat] lyp->nfsly_lastbyte); > ^~~~~~~~~~~~~~~~~~~ > /usr/src/sys/fs/nfs/nfscl.h:74:11: note: expanded from macro > 'NFSCL_DEBUG' printf(__VA_ARGS__); \ > ^ > 3 errors generated. > *** Error code 1 > > Stop. > > > Regards, > Oliver
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALCpEUG98BmK5Hh58xWPr4d39VgptpoTfsjnEj-1Phk5VM213g>