From: Loganaden Velvindron <loganaden@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Fresh from the bakery
Date: Fri, 16 Oct 2015 17:37:56 +0400 [thread overview]
Message-ID: <CAOp4FwQi-4JmjUHeQpzUSW9HOqMTK2Y3WmuVUUhXE-DGvXYEbw@mail.gmail.com> (raw)
In-Reply-To: <5620FB43.1080100@darbyshire-bryant.me.uk>
[-- Attachment #1: Type: text/plain, Size: 2567 bytes --]
On Fri, Oct 16, 2015 at 5:27 PM, Kevin Darbyshire-Bryant <
kevin@darbyshire-bryant.me.uk> wrote:
>
>
> On 16/10/15 11:24, Loganaden Velvindron wrote:
> >
> >
> > On Fri, Oct 16, 2015 at 1:39 PM, Loganaden Velvindron
> > <loganaden@gmail.com <mailto:loganaden@gmail.com>> wrote:
> >
> >
> >
> > Building the latest tc-adv causes issues with gcc.
> >
> >
> > gcc -Wall -Wstrict-prototypes -Wmissing-prototypes
> > -Wmissing-declarations -Wold-style-definition -Wformat=2 -O2
> > -I../include -DRESOLVE_HOSTNAMES -DLIBDIR=\"/usr/lib\"
> > -DCONFDIR=\"/etc/iproute2\" -D_GNU_SOURCE -DHAVE_SETNS -DHAVE_ELF
> > -DCONFIG_GACT -DCONFIG_GACT_PROB
> > -DIPT_LIB_DIR=\"/usr/lib/iptables\" -DYY_NO_INPUT -c -o
> > q_cake0.o q_cake0.c
> > In file included from q_cake.c:48:0:
> > q_cake.c: In function
> > ‘cake_print_xstats’:../include/utils.h:177:55: error: expected
> > expression before ‘)’ token # define offsetof(type, member) (
> > (size_t) & ( (type *) 0 )->member )
> > ^q_cake.c:500:31: note: in expansion of
> > macro ‘offsetof’
> > && RTA_PAYLOAD(xstats) >= offsetof(*stnc, capacity_estimate))
> >
> > GCC version:
> > gcc version 5.2.0 (GCC)
> >
> >
> > The commit causing the issue is this one:
> >
> >
> https://github.com/dtaht/tc-adv/commit/9b2dc094b2b1526ec4222efc1b0a1d02812def5a
> >
> > I'm not sure about the fix. here is it:
> >
> > https://github.com/dtaht/tc-adv/pull/7
> >
> >
> >
> Hi Logan,
>
> Thanks for the report. It breaks here too :-( I'm annoyed with myself
> for merging the latest, latest, latest commits (around 02:00 my time)
> early this morning without at least compile testing them. I think it
> was about 05:00 whilst doing an overnight shift (Aussie MotoGP) and the
> box I did it on is a little out of date and slow (would require a
> toolchain rebuild which is about 4 hours!) Normally I at least compile
> test. Oh well, move on...
>
> I'm sure Jonathan will pick this up shortly - In fact as I type this
> after just compile testing & installing your fix I notice that he has :-)
>
> Logan, thanks very much for your fix, it's appreciated. I will however
> close your pull request and merge in the (identical!) fix from upstream
> to keep the git histories a little closer.
>
>
Thanks for updating the master tree. I was working on another issue, when I
encountered this problem with the latest sync :)
> Cheers,
>
> Kevin
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 3769 bytes --]
prev parent reply other threads:[~2015-10-16 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 11:55 Kevin Darbyshire-Bryant
2015-10-16 1:11 ` Jonathan Morton
2015-10-16 9:39 ` Loganaden Velvindron
2015-10-16 10:24 ` Loganaden Velvindron
2015-10-16 13:18 ` Jonathan Morton
2015-10-16 13:27 ` Kevin Darbyshire-Bryant
2015-10-16 13:37 ` Loganaden Velvindron [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOp4FwQi-4JmjUHeQpzUSW9HOqMTK2Y3WmuVUUhXE-DGvXYEbw@mail.gmail.com \
--to=loganaden@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=kevin@darbyshire-bryant.me.uk \
/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