Ibr-dtn February 2013

ibr-dtn@ibr.cs.tu-bs.de

5 participants
10 discussions

safety wrapper for IBR-DTN daemon
by Francisco Cuesta 22 Feb '13

22 Feb '13

Good morning, I'm keen on running dtn daemon on another platform and I have found the safety-wrapper.sh on the recipes for OpenWRT. According to the script, after system check it tries to mount the container making use of mountcontainer.sh, my doubt is whether other OS like fedora or ububtu need to have this script too or not. I mean, if I have got the daemon bin, do I have to create a container (for instance on fedora os) as is done on that script before running the daemon bin, or just with proper configuration file and the daemon bin it's enough to start and run the ibrtdtn daemon? Thanks in advance, Regards.

2 1

Re: [ibr-dtn] Compiling ibrdtn on Eclipse
by Sebastian Schildt 22 Feb '13

22 Feb '13

As you can see here http://packages.debian.org/wheezy/libdaemon0 libdaemon should run everywhere. I guess it is not installed correctly in your environment (Not in the library path or something). So if you install libdaemon on the target it should work. There might be an configure option to deactivate libdameon. Something like --without-libdaemon. I am not exactly sure about the exact option atm. Or you can just remove libdaemon devel heders from your build machine. Then configure should detect it and deactivate it. Sebastian Am 13.02.2013 um 10:11 schrieb Francisco Cuesta <ndarkness(a)gmail.com>: > The problem is that I'm trying to crosscompile ibrdtn suite (ibrcommons, ibrdtn, ibrdtnd,ibrdtn-tools) for an ARM architecture. I was using the ./configure provided by ibrdtn suite to make my target (--build=i686-linux --host=arm-mv5sft-linux-gnueabi --target=arm-mv5sft-linux-gnueabi)but when crosscompiling the ibrdtnd complains that it cannot find the library libdaemon so I thought I had to crosscompile it for my ARM architecure, but I think that the libdaemon doesn't support the arm architecture, because of that I wanted to know how you did the crosscompile it. > > Thanks, > > Fran > > > 2013/2/13 Sebastian Schildt <schildt(a)ibr.cs.tu-bs.de> > Hello, > > Platforms like Raspberry are easy, you can just compile directly on the target. Maybe that is an option in your case? I think our build server uses a qemu environment so we do not need to integrate a physical Pi into our build infrastructure. Both ways are not the fastest, but work pretty well. At least in the case of qemu you can just throw more processing power in..... > AFAIK we do nothing special to compile libdaemon on this platform. What is the problem? > > > MfG > > Sebastian > > Am 13.02.2013 um 08:55 schrieb Francisco Cuesta <ndarkness(a)gmail.com>: > >> Good morning, >> >> I still trying to cross-compile the project to an ARM architecture, I have noticed that you could create the projects packets for RasperriPi, which I assume contains an ARM processor. >> May you tell me how you did the crosscompilation for this platform?? I'm specially interested on how you did the crosscompilation of libdaemon library for arm since I'm getting trouble in achieve the same goal. >> >> Thanks in advance, >> >> Regards, >> >> Fran >> >> >> 2013/2/4 Johannes Morgenroth <morgenroth(a)ibr.cs.tu-bs.de> >> Hello, >> >> > I'm having an issue when I try to crosscompile ibrdtn-tools,I think I >> > have been able to crosscompile ibrcommon, ibrdtn and ibrdtnd but with >> > the last package ibrdtn-tools while crosscompiling I was retreived >> > this error >> >> > I know how to fix it through linux terminal, but non through Eclipse >> > or autotools pluging, since the settings of the project aren't >> > available. May you enlighten me? >> > >> once again: I have NEVER done cross-compiling using eclipse! So I can >> not assist you with those issues. >> > >> > On the other hand, I'm wondering why you did disable the project C/C++ >> > settings? >> > >> And as I have written in my email of 2013/1/22: >> >> The path in your eclipse project depends on you specific system. Thus, >> it is not a solution to just copy the path settings from somebody else. >> The best way for you is to import the project as C++ autotools project. >> In this case eclipse will set the right default paths settings. >> >> >> Johannes >> >> >> -- >> !! This message is brought to you via the `ibr-dtn' mailing list. >> !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust >> !! your settings, send a mail message to <ibr-dtn-request(a)ibr.cs.tu-bs.de> >> !! or look at https://www.ibr.cs.tu-bs.de/mailman/listinfo/ibr-dtn. > >

2 1

dtninbox/dtnoutbox
by Bruno Tavares 21 Feb '13

21 Feb '13

Hello. I just started to use ibr-DTN. I used dtnsend and dtnrecv and they worked. Now I'm trying to use dtninbox/dtnoutbox and it is not working well (probably I'm doing something wrong). First i used the comand: bruno@bruno:~$ dtnoutbox abc /home/bruno/Desktop/gg/ dtn://default-1015PEM files: Untitled2 On the other PC I used: dtninbox abc /home/default/Desktop/ And nothing happens In the deamon i noticed the following messages on the receiving node: Wed Feb 20 11:07:28 2013 NOTICE: BundleReceivedEvent: Bundle received [414673649.245] dtn://bruno/abc -> dtn://default-1015PEM from dtn://bruno Wed Feb 20 11:07:28 2013 NOTICE: QueueBundleEvent: New bundle queued [414673649.245] dtn://bruno/abc Wed Feb 20 11:07:28 2013 NOTICE: BundleEvent: bundle [414673649.245] dtn://bruno/abc received Wed Feb 20 11:07:28 2013 NOTICE: BundleEvent: bundle [414673649.245] dtn://bruno/abc deleted Wed Feb 20 11:07:28 2013 NOTICE: BundlePurgeEvent: purging bundle [414673649.245] dtn://bruno/abc Can somebody help me? Thank you Bruno Tavares

2 1

Re: [ibr-dtn] Android Apps Neighbor Discovery
by justin＠gardettoengineering.com 20 Feb '13

20 Feb '13

2 1

Re: [ibr-dtn] Android Apps Neighbor Discovery
by justin＠gardettoengineering.com 15 Feb '13

15 Feb '13

2 1

Re: [ibr-dtn] Compiling ibrdtn on Eclipse
by Francisco Cuesta 13 Feb '13

13 Feb '13

Good morning, I still trying to cross-compile the project to an ARM architecture, I have noticed that you could create the projects packets for RasperriPi, which I assume contains an ARM processor. May you tell me how you did the crosscompilation for this platform?? I'm specially interested on how you did the crosscompilation of libdaemon library for arm since I'm getting trouble in achieve the same goal. Thanks in advance, Regards, Fran 2013/2/4 Johannes Morgenroth <morgenroth(a)ibr.cs.tu-bs.de> > Hello, > > > I'm having an issue when I try to crosscompile ibrdtn-tools,I think I > > have been able to crosscompile ibrcommon, ibrdtn and ibrdtnd but with > > the last package ibrdtn-tools while crosscompiling I was retreived > > this error > > > I know how to fix it through linux terminal, but non through Eclipse > > or autotools pluging, since the settings of the project aren't > > available. May you enlighten me? > > > once again: I have NEVER done cross-compiling using eclipse! So I can > not assist you with those issues. > > > > On the other hand, I'm wondering why you did disable the project C/C++ > > settings? > > > And as I have written in my email of 2013/1/22: > > The path in your eclipse project depends on you specific system. Thus, > it is not a solution to just copy the path settings from somebody else. > The best way for you is to import the project as C++ autotools project. > In this case eclipse will set the right default paths settings. > > > Johannes > >

2 1

(no subject)
by Francisco Cuesta 08 Feb '13

08 Feb '13

Hello, I'm trying to cross-compile the project for an arm-mv5sft-linux-gnueabi processor,I have set the ./configure in this way on the terminal ./configure --build=i686-linux --host=arm-mv5sft-linux-gnueabi --target=arm-mv5sft-linux-gnueabi CC=~/s/arm-mv5sft-linux-gnueabi/SW3.2p1/bin/arm-mv5sft-linux-gnueabi-gcc CXX=~/s/arm-mv5sft-linux-gnueabi/SW3.2p1/bin/arm-mv5sft-linux-gnueabi-g++ LD=~/s/arm-mv5sft-linux-gnueabi/SW3.2p1/arm-mv5sft-linux-gnueabi/bin/arm-mv5sft-linux-gnueabi-ld LDFLAGS=-L/usr/include/libdaemon --with-sysroot=/home/thales/s/arm-mv5sft-linux-gnueabi/SW3.2p1/arm-mv5sft-linux-gnueabi --prefix=/justInstalled --disable-shared --enable-threads=posix --enable-long-long --enable-target-optspace --disable-nls --with-float=soft --disable-multilib --enable-symvers=gn The configuration succeeded, however when I do make I got an inclusion error libtool: link: warning: library `/home/j/s/arm-mv5sft-linux-gnueabi/SW3.2p1/bin/../lib/gcc/arm-mv5sft-linux-gnueabi/4.3.2/../../../../arm-mv5sft-linux-gnueabi/lib/libstdc++.la' was moved. CXX Main.o Main.cpp:28:30: error: libdaemon/daemon.h: No such file or directory Main.cpp: In function 'int __daemon_run()': Main.cpp:175: error: 'daemon_retval_send' was not declared in this scope . . . make[1]: Leaving directory `/home/j/ibrdtn-svn/daemon' make: *** [all-recursive] Error 1 I've checked out that I have installed the libdeamon @ubuntu:~$ pkg-config --libs libdaemon -ldaemon @ubuntu:~$locate libdaemon /usr/include/libdaemon /usr/include/libdaemon/daemon.h /usr/include/libdaemon/dexec.h /usr/include/libdaemon/dfork.h /usr/include/libdaemon/dlog.h /usr/include/libdaemon/dnonblock.h /usr/include/libdaemon/dpid.h /usr/include/libdaemon/dsignal.h /usr/lib/libdaemon.a /usr/lib/libdaemon.so /usr/lib/libdaemon.so.0 /usr/lib/libdaemon.so.0.5.0 /usr/lib/pkgconfig/libdaemon.pc Why the inclusion is wrong?? I've tried to include using ./configure (as before) LDFLAGS=-llibdeamon (as before) ./configure (as before) LIBS=-llibdeamon (as before) But the configure tell me that there's an error, and I have to read the conf.log, which says /home/j/s/arm-mv5sft-linux-gnueabi/SW3.2p1/bin/../lib/gcc/arm-mv5sft-linux-gnueabi/4.3.2/../../../../arm-mv5sft-linux-gnueabi/bin/ld: cannot find -llibdeamon collect2: ld returned 1 exit status Any idea would be very much appreciated! Thanks in advance, Regards

1 0

Re: [ibr-dtn] Compiling ibrdtn on Eclipse
by Francisco Cuesta 06 Feb '13

06 Feb '13

Good moring, Sorry for repeating myself on the previous mail... I was testing some other crosscompilations with other archicture, a arm-linux-gnueabi, using linux (ubuntu) terminal in order to check whether the parameters which I impose are correct or not. Thus, I have made use of ./configure like this *./configure --build=i686-linux --host=arm-mv5sft-linux-gnueabi --target=arm-mv5sft-linux-gnueabi CC=/home/t/s/arm-mv5sft-linux-gnueabi/SW3.2p1/bin/arm-mv5sft-linux-gnueabi-gcc CXX=/home/t/s/arm-mv5sft-linux-gnueabi/SW3.2p1/bin/arm-mv5sft-linux-gnueabi-g++ --with-gnu-ld --with-sysroot=/h/t/s/arm-mv5sft-linux-gnueabi/SW3.2p1/arm-mv5sft-linux-gnueabi CFLAGS="-m32" LDFLAGS="-m32" --prefix=/ibrdtn-svn/dtnCross/* However, after chenking the configure output (I've attached a snippet below) I have realized that the compilers aren't set properly, should I include the path where the compiler are in instead of setting the flags? ... checking for arm-mv5sft-linux-gnueabi-g++... no checking for arm-mv5sft-linux-gnueabi-c++... no checking for arm-mv5sft-linux-gnueabi-gpp... no checking for arm-mv5sft-linux-gnueabi-aCC... no checking for arm-mv5sft-linux-gnueabi-CC... no checking for arm-mv5sft-linux-gnueabi-cxx... no checking for arm-mv5sft-linux-gnueabi-cc++... no checking for arm-mv5sft-linux-gnueabi-cl.exe... no checking for arm-mv5sft-linux-gnueabi-FCC... no checking for arm-mv5sft-linux-gnueabi-KCC... no checking for arm-mv5sft-linux-gnueabi-RCC... no checking for arm-mv5sft-linux-gnueabi-xlC_r... no checking for arm-mv5sft-linux-gnueabi-xlC... no ... Thanks in advance, Regards, Francisco 2013/2/4 Johannes Morgenroth <morgenroth(a)ibr.cs.tu-bs.de> > Hello, > > > I'm having an issue when I try to crosscompile ibrdtn-tools,I think I > > have been able to crosscompile ibrcommon, ibrdtn and ibrdtnd but with > > the last package ibrdtn-tools while crosscompiling I was retreived > > this error > > > I know how to fix it through linux terminal, but non through Eclipse > > or autotools pluging, since the settings of the project aren't > > available. May you enlighten me? > > > once again: I have NEVER done cross-compiling using eclipse! So I can > not assist you with those issues. > > > > On the other hand, I'm wondering why you did disable the project C/C++ > > settings? > > > And as I have written in my email of 2013/1/22: > > The path in your eclipse project depends on you specific system. Thus, > it is not a solution to just copy the path settings from somebody else. > The best way for you is to import the project as C++ autotools project. > In this case eclipse will set the right default paths settings. > > > Johannes > >

1 0

Re: [ibr-dtn] Android Apps Neighbor Discovery
by justin＠gardettoengineering.com 04 Feb '13

04 Feb '13

2 1

Re: [ibr-dtn] Compiling ibrdtn on Eclipse
by Francisco Cuesta 04 Feb '13

04 Feb '13

Hello, I have a question concerning to how did you cross-compile ibtrdt suite for openwrt in a terminal first you configure ibrdtn project with ./configure indicating that the target was a mips processor and you passed as compiler the one in hte toolchain of OpenWRT, am I mistaken? Thanks in advance Regards, 2013/1/25 Francisco Cuesta <ndarkness(a)gmail.com> > Hi Johannes, > > Understood, concerning to the crosscompilation with eclipse I know how to > do it for my target, however the error when I try to crosscompile ibrdtn > project on eclipse is a reference one, since it always complains about the > path of some files inside the project which cannot be reached, that's to > say, it complains about the sentences include <ibrdtn/utils/Uitls.h> for > instance, because it cannot find the file (or the path I guess) and says > that such a file does not exist. May you tell me how how to reference the > project inside folders in order other subfolders can reach then avoiding > this reference problem? I tried to look it into the project settings (which > were downloaded too) but I couldn't find them. > > Thank you so much > > Kind regards > > Fran > > > 2013/1/24 Johannes Morgenroth <morgenroth(a)ibr.cs.tu-bs.de> > >> Both. In a terminal using the OpenWRT toolchain. >> >> -------- Weitergeleitete Nachricht -------- >> Von: Francisco Cuesta <ndarkness(a)gmail.com> >> An: Johannes Morgenroth <morgenroth(a)ibr.cs.tu-bs.de> >> Betreff: Re: [ibr-dtn] Compiling ibrdtn on Eclipse >> Datum: Thu, 24 Jan 2013 14:29:46 +0100 >> >> I see, then when you compiled the code forn Openwrt for instance, did >> you make it through a terminal or wiht openwrt toolchain?? >> >> >

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Ibr-dtn February 2013