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@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