On Mon, May 18, 2009 at 1:14 AM, Hichem Boussetta
> Hichem Boussetta a écrit :
>> Hi all,
>> It is the first time that I use ltp and I am having some troubles trying
>> to cross compile it.
>> I have seen a cross compilation example in the installation manual. It is
>> about cross compiling for a powerpc processor.
>> CROSS_CFLAGS= -mpowerpc64
>> LOADLIBES=-lpthread -lc -lresolv -lnss_dns -lnss_files -lm -lc
>> export LOADLIBES LIB_DIR
>> In my case, I a compiling for an arm processor. I tried to do the same by
>> the specifying the toolchain prefix, the CC, LD, AR and the LIB_DIR. But, I
>> get always this error when cross compiling :
>> getdelays.c: In function 'print_delayacct':
>> getdelays.c:215: error: 'struct taskstats' has no member named
>> getdelays.c:216: error: 'struct taskstats' has no member named
>> make: *** [getdelays] Erreur 1
>> In fact, I omitted the libraries nss_dns and lnss_files since didn't find
>> them in the lib directories of my toolchain. I am not sure about that, but I
>> don't think the problem is related to this libraries since they do not exist
>> in my host machine either, and here, the compilation of ltp worked well.
>> Perhaps, the problem is due to the fact that I didn't put any option in the
>> CROSS_CFLAGS since I found nowhere how to get this information.
>> If someone knows any thing about this or succeeded to cross compile ltp,
>> it would be really nice if he could tell me, because I am really stuck now
> Hi all,
> I think that I've figured out how to configure LTP for cross
> compilation. In fact, we need to put the right parameters during the
> configuration. We should append the cross toolchain's bin directory to
> the path and add --host=$(toolchain_prefix) to the configure script. By
> doing that, ltp succeds to find out the binary utilities that it should
> use (gcc, ld ,ar, ranlib, ...). We should also specify the path to the
> include and lib directory of the toolchain we are using by setting the
> variables CPPFLAGS and LDFLAGS. However, I still get a compilation error
> that I think it is related to the fact that some libraries are missing
> (signalfd for example). The message I receive is this :
> getdelays.c: In function 'print_delayacct':
> getdelays.c:215: error: 'struct taskstats' has no member named
> getdelays.c:216: error: 'struct taskstats' has no member named
> Does anyone know how to overcome this problem or does this mean that it
> is not possible to cross compile LTP ? In fact, the crosstoolchains I am
> using are generated using crosstool-ng. So, I don't think that the
> problem is due to the toolchain.
Your code may be mismatched with the testcode which means the autoconf
stuff needs to be fixed.