From: chrubis@suse.cz
To: vikas bisla <vikasbisla15@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Compling LTP for android Using Ndk revision 8
Date: Thu, 20 Sep 2012 16:37:31 +0200 [thread overview]
Message-ID: <20120920143731.GD7902@saboteur.suse.cz> (raw)
In-Reply-To: <CALFGhcTOGwfj=WQJL8FJn8q8LsEPe3fD+KEJBTjidxM47=PL6A@mail.gmail.com>
Hi!
> We are trying to compile LTP for android using NDK tool chain.
>
> Flags set while configuration-
>
> ./configure --host=arm-eabi
> CC=/home/vikas/Desktop/LTP/arm-eabi-4.4.3/bin/arm-eabi-gcc
> CPPFLAGS="-I/home/vikas/Desktop/android-ndk-r8b/platforms/android-14/arch-arm/usr/include/"
> CFLAGS="-nostdlib"
> LDFLAGS="-Wl,-rpath-link=/home/vikas/Desktop/android-ndk-r8b/platforms/android-14/arch-arm/usr/lib/
> -L/home/vikas/Desktop/android-ndk-r8b/platforms/android-14/arch-arm/usr/lib/"
> LIBS="-lc"
>
> After Config we are doing
>
> Make ARCH=arm
>
> it is giving following error.
>
> /Desktop/LTP/ltp-full-20120903$ make ARCH=arm
> make -C "lib" \
> -f "/home/vikas/Desktop/LTP/ltp-full-20120903/lib/Makefile" all
> make[1]: Entering directory `/home/vikas/Desktop/LTP/ltp-full-20120903/lib'
> /home/vikas/Desktop/LTP/arm-eabi-4.4.3/bin/arm-eabi-gcc -nostdlib -g -O2
> -fno-strict-aliasing -pipe -Wall
> -I/home/vikas/Desktop/android-ndk-r8b/platforms/android-14/arch-arm/usr/include/
> -I../include -I../include -I../include -I../include -c -o
> bytes_by_prefix.o bytes_by_prefix.c
> bytes_by_prefix.c: In function 'bytes_by_prefix':
> bytes_by_prefix.c:94: error: 'B_MULT' undeclared (first use in this
> function)
> bytes_by_prefix.c:94: error: (Each undeclared identifier is reported only
> once
> bytes_by_prefix.c:94: error: for each function it appears in.)
> bytes_by_prefix.c: In function 'lbytes_by_prefix':
> bytes_by_prefix.c:142: error: 'B_MULT' undeclared (first use in this
> function)
> bytes_by_prefix.c: In function 'llbytes_by_prefix':
> bytes_by_prefix.c:193: error: 'B_MULT' undeclared (first use in this
> function)
> make[1]: *** [bytes_by_prefix.o] Error 1
> make[1]: Leaving directory `/home/vikas/Desktop/LTP/ltp-full-20120903/lib'
> make: *** [lib-all] Error 2
>
> Can anybody please suggest some pointer so that we can go forward.
Look at the lib/bytes_by_prefix.c there are ugly ifdefs that comes from
legacy code that are trying to figure out disk block size. Just define
the B_MULT to someting reasonable like 4k to continue.
And that rises question whether are these still needed and if so what is
reasonable default...
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://ad.doubleclick.net/clk;258768047;13503038;j?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2012-09-20 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 12:16 [LTP] Compling LTP for android Using Ndk revision 8 vikas bisla
2012-09-04 1:41 ` cxie
2012-09-20 14:37 ` chrubis [this message]
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=20120920143731.GD7902@saboteur.suse.cz \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=vikasbisla15@gmail.com \
/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