public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Gus Wirth <gwirth79@gmail.com>
To: b.a.t.m.a.n@lists.open-mesh.net
Subject: [B.A.T.M.A.N.] batman-adv compile fails with DEBUG on
Date: Wed, 02 Dec 2009 09:31:23 -0800	[thread overview]
Message-ID: <4B16A46B.9020909@gmail.com> (raw)

When trying to compile batman-adv revision 1489 checked out from 
Subversion I get a failure if I activate debugging by editing the 
appropriate line in Makefile.kbuild. The error is:

   CC [M]  /home/gus/src/batman/svn-trunk/batman-adv-kernelland/originator.o
/home/gus/src/batman/svn-trunk/batman-adv-kernelland/originator.c: In 
function ‘purge_orig_neigbours’:
/home/gus/src/batman/svn-trunk/batman-adv-kernelland/originator.c:182: 
error: ‘orig_str’ undeclared (first use in this function)
/home/gus/src/batman/svn-trunk/batman-adv-kernelland/originator.c:182: 
error: (Each undeclared identifier is reported only once
/home/gus/src/batman/svn-trunk/batman-adv-kernelland/originator.c:182: 
error: for each function it appears in.)
make[2]: *** 
[/home/gus/src/batman/svn-trunk/batman-adv-kernelland/originator.o] Error 1
make[1]: *** 
[_module_/home/gus/src/batman/svn-trunk/batman-adv-kernelland] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.30.9-99.fc11.i686.PAE'
make: *** [all] Error 2

This was caused by revision 1488 and the originator.c file.

I've looked at the Trac system on the web site and it doesn't appear 
that the ticket system gets used much, if at all. Should I also post 
this to the Trac system or is this the right way to do this?

Gus

             reply	other threads:[~2009-12-02 17:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02 17:31 Gus Wirth [this message]
2009-12-03  2:48 ` [B.A.T.M.A.N.] batman-adv compile fails with DEBUG on Marek Lindner
2009-12-03  3:12   ` Gus Wirth
2009-12-03  3:48     ` Marek Lindner

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=4B16A46B.9020909@gmail.com \
    --to=gwirth79@gmail.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.net \
    /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