From: Kevin Brosius <cobra@compuserve.com>
To: Jens Axboe <axboe@suse.de>
Cc: "David S. Miller" <davem@redhat.com>,
kernel <linux-kernel@vger.kernel.org>
Subject: Re: bk current build failures (xfrm.h / tpqic02.c)
Date: Thu, 14 Nov 2002 22:22:30 -0500 [thread overview]
Message-ID: <3DD46876.66725D8E@compuserve.com> (raw)
In-Reply-To: 20021114123440.GK847@suse.de
Jens Axboe wrote:
>
>
> On Wed, Nov 13 2002, David S. Miller wrote:
> > On Wed, 2002-11-13 at 16:40, Kevin Brosius wrote:
> > > net/core/skbuff.c: At top level:
> > > include/net/xfrm.h:104: storage size of `lft' isn't known
> > > include/net/xfrm.h:112: storage size of `replay' isn't known
> > > include/net/xfrm.h:115: storage size of `stats' isn't known
> > > include/net/xfrm.h:117: storage size of `curlft' isn't known
> > > make[2]: *** [net/core/skbuff.o] Error 1
> >
> > Something is wrong with your tree, net/xfrm.h includes linux/xfrm.h
> > which declares the layout of said structures the compiler is
> > complaining about.
>
> Most likely he is building out of his bk tree and he forgot to bk get
> the files again.
Yes, that's it. Thank you, and sorry about that. (I'll go configure
for checkout-get mode now...)
Now I see:
drivers/char/tpqic02.c: In function `__initfn':
drivers/char/tpqic02.c:2798: parse error before "void"
make[2]: *** [drivers/char/tpqic02.o] Error 1
I'm guessing that may be fixed in 2.5.47-ac2[&4]?
--
Kevin
prev parent reply other threads:[~2002-11-15 3:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 0:40 bk current build failures (xfrm.h / tpqic02.c) Kevin Brosius
2002-11-14 4:17 ` David S. Miller
2002-11-14 12:34 ` Jens Axboe
2002-11-15 3:22 ` Kevin Brosius [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DD46876.66725D8E@compuserve.com \
--to=cobra@compuserve.com \
--cc=axboe@suse.de \
--cc=davem@redhat.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox