Good morning,

After so much struggling with it, I think as Sebastian told me, my problem is owed to Ubuntu 12.04LTS, I cannot understand the reason I suspect  something related with a bad link on the libraries or whatever... The point is that on Fedora 18 it worked perfectly so I'm thinking that I'm going to work with it from now.

Thanks very much for your help.

Regards


2013/2/13 Sebastian Schildt <schildt@ibr.cs.tu-bs.de>
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@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@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@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@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@ibr.cs.tu-bs.de>
!! or look at https://www.ibr.cs.tu-bs.de/mailman/listinfo/ibr-dtn.