public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Hichem Boussetta <boussettahichem@yahoo.fr>
To: Hichem Boussetta <boussettahichem@yahoo.fr>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] LTP cross compilation
Date: Mon, 18 May 2009 10:14:33 +0200	[thread overview]
Message-ID: <4A1118E9.1000501@yahoo.fr> (raw)
In-Reply-To: <4A1067FE.8080501@yahoo.fr>


[-- Attachment #1.1.1: Type: text/plain, Size: 2902 bytes --]

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_COMPILER=/opt/ppc64/powerpc64-linux/bin/powerpc64-linux-
> CROSS_CFLAGS= -mpowerpc64
> LDFLAGS=-static
> LOADLIBES=-lpthread -lc -lresolv -lnss_dns -lnss_files -lm -lc
> LIB_DIR=/lib64
> 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 
> 'freepages_count'
> getdelays.c:216: error: 'struct taskstats' has no member named 
> 'freepages_delay_total'
> make[5]: *** [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 :-)
>
> Thanks,
>
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
'freepages_count'
getdelays.c:216: error: 'struct taskstats' has no member named
'freepages_delay_total'

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.

Regards,

-- 
Hichem BOUSSETTA
Elève ingénieur
Ecole Polytechnique de Tunisie




[-- Attachment #1.1.2: boussettahichem.vcf --]
[-- Type: text/x-vcard, Size: 366 bytes --]

begin:vcard
fn:Hichem
n:Boussetta;Hichem
org;quoted-printable:Ecole Polytechnique de Tunisie;Signaux et syst=C3=A8mes
adr:;;;La marsa;Tunis;2078;Tunisie
email;internet:boussettahichem@yahoo.fr
title;quoted-printable:El=C3=A8ve ing=C3=A9nieur
tel;cell:(+216) 21 149 549
note:Date de naissance : 17-04-1986
url:http://hichem.boussetta.netcv.fr/
version:2.1
end:vcard


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3278 bytes --]

[-- Attachment #2: Type: text/plain, Size: 334 bytes --]

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables 
unlimited royalty-free distribution of the report engine 
for externally facing server and web deployment. 
http://p.sf.net/sfu/businessobjects

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2009-05-18  9:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-17 19:39 [LTP] LTP cross compilation Hichem Boussetta
2009-05-18  8:14 ` Hichem Boussetta [this message]
2009-05-29 11:55   ` Garrett Cooper
  -- strict thread matches above, loose matches on Subject: below --
2015-09-23  7:13 kamal p
2015-09-24  2:43 ` $rik

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=4A1118E9.1000501@yahoo.fr \
    --to=boussettahichem@yahoo.fr \
    --cc=ltp-list@lists.sourceforge.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