From: Stephen Hemminger <stephen@networkplumber.org>
To: nello martuscielli <ppc.addon@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: iproute-3.8.0 build error on Linux ppc64
Date: Wed, 27 Feb 2013 07:28:30 -0800 [thread overview]
Message-ID: <20130227072830.6ab4373e@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <CABMX=WxaxNhvx4YA6-KiDjoRURXsotCSEpxQJu4mK11UtW78jw@mail.gmail.com>
On Wed, 27 Feb 2013 06:37:46 +0100
nello martuscielli <ppc.addon@gmail.com> wrote:
> sorry, it was your previous commit about -Werror
>
> thanks,
> Nell
>
>
>
> On Wed, Feb 27, 2013 at 6:08 AM, nello martuscielli <ppc.addon@gmail.com> wrote:
> > hi,
> > after your commit:
> > http://git.kernel.org/?p=linux/kernel/git/shemminger/iproute2.git;a=commitdiff;h=6398d3a65277a2ebed085ad9deef15fea6f4ed09
> >
> > specifically -Wmissing-prototypes and I get this error on Linux ppc64
> >
> > gcc -Wall -Wstrict-prototypes -Werror -Wmissing-prototypes
> > -Wmissing-declarations -Wold-style-definition -O2 -I../include
> > -DRESOLVE_HOSTNAMES -DLIBDIR=\"/usr/lib\" -DCONFDIR=\"/etc/iproute2\"
> > -D_GNU_SOURCE -c -o ipntable.o ipntable.c
> > cc1: warnings being treated as errors
> > ipntable.c: In function 'print_ntable':
> > ipntable.c:435:3: error: format '%llu' expects type 'long long
Pushed up a fix for this using casts.
Would rather have used inttypes.h but that was incompatible with kernel's __u64.
next prev parent reply other threads:[~2013-02-27 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABMX=WwSNeTq_ascBRxJtQrsErR-cFODZQh_wrim6K8weyLDtQ@mail.gmail.com>
2013-02-27 5:15 ` iproute-3.8.0 build error on Linux ppc64 nello martuscielli
2013-02-27 5:39 ` nello martuscielli
[not found] ` <CABMX=WxaxNhvx4YA6-KiDjoRURXsotCSEpxQJu4mK11UtW78jw@mail.gmail.com>
2013-02-27 15:28 ` Stephen Hemminger [this message]
2013-02-27 16:27 ` nello martuscielli
2013-02-27 20:53 ` Denis Kirjanov
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=20130227072830.6ab4373e@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=ppc.addon@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