From: Andreas Langer <a.langer@q-dsl.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] battool Speicherzugriffsfehler (update - strace/ldd output)
Date: Fri, 24 Aug 2007 13:05:34 +0200 [thread overview]
Message-ID: <46CEBB7E.4020809@q-dsl.de> (raw)
In-Reply-To: <46CEB78B.7050403@saxnet.de>
hello robert, sorry i forgot an usage message when you run battool
without an argument.
please use battool -h too see how you use this tool.
i will fix this soon. thx
Robert Tulke wrote:
> Robert Tulke schrieb:
>> Hello i use the latest batman-advanced svn from trunk
>>
>> zeus:/usr/src/# svn co https://dev.open-mesh.net/svn/batman/trunk/
>> ...
>> ...
>>
>> zeus:/usr/src/# cd trunk/batman-advanced/batool
>>
>> zeus:/usr/src/batman-advanced/battool# make clean
>> rm -f battool *.o *~
>>
>> zeus:/usr/src/batman-advanced/battool# make
>> gcc -Wall -O0 -g -c -o battool.o battool.c
>> gcc -Wall -O0 -g -c -o batping.o batping.c
>> gcc -Wall -O0 -g -c -o functions.o functions.c
>> gcc -Wall -O0 -g -c -o batroute.o batroute.c
>> gcc -Wall -O0 -g -c -o batdump.o batdump.c
>> gcc -Wall -O0 -g -c -o list-batman.o list-batman.c
>> gcc -lpthread battool.o batping.o functions.o batroute.o batdump.o
>> list-batman.o -o battool
>>
>> <- looks good but:
>>
>> zeus:/usr/src/batman-advanced/battool# ./battool
>> Speicherzugriffsfehler
>>
>> i use Debian Etch 4.0 with latest upgrades
> http://paste.debian.net/35349
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
>
next prev parent reply other threads:[~2007-08-24 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 10:27 [B.A.T.M.A.N.] battool Speicherzugriffsfehler Robert Tulke
2007-08-24 10:48 ` [B.A.T.M.A.N.] battool Speicherzugriffsfehler (update - strace/ldd output) Robert Tulke
2007-08-24 11:05 ` Andreas Langer [this message]
2007-08-24 11:16 ` Robert Tulke
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=46CEBB7E.4020809@q-dsl.de \
--to=a.langer@q-dsl.de \
--cc=b.a.t.m.a.n@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