This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: systemTap 1.0 CROSS COMPILE


Hi Frank,


Thanks for the valuable information.
The process is going successfully.

Build  .ko on Host machine and insert the .ko with staprun on the Target.

ON HOST: stap
I have build stap on HOST Machine.
(With out any cross compilations)

#./configure --with-elfutils=elfutils/ --prefix=/usr/local/arm/cross/devel
#make
#make install
# cd testsuite
# cd buildok
# stap -a arm -B CROSS_COMPILE=/usr/local/arm/cross/devel/bin/arm-dev-
-p4 -vv -r  2.6.29.4-kzm-arm11-g7b68317 -m  array_size array_size.stp
/*  build pass and array_size.ko */
/* transfer this .ko file to Target Machine */

ON TARGET: staprun.
I have build staprun on Target Machine.

#./configure --with-elfutils=elfutils/ --prefix=/tool/devel/
#make
#make install
/* staprun with .ko build on HOST Machine */
#staprun array_size.ko
#


However, I am not sure the configure --host, -- target, --build options yet.
Let me try these options some other time.

Best regards,
Naresh Kamboju



On Wed, Oct 28, 2009 at 8:18 PM, Frank Ch. Eigler <fche@redhat.com> wrote:
> Hi -
>
> On Wed, Oct 28, 2009 at 06:23:18PM +0530, naresh kamboju wrote:
>> > Try instead
>> > .../configure --target=arm... --prefix=... --with-elfutils=... --disable-translator
>>
>> I have tried in different ways to cross compile using installed
>> /usr/local/arm tool chain.
>> However, the stap and staprun are created in X86 format again.
>
> Right, modern autoconf likes to have "--build=HOST --host=TARGET"
> instead of "--target=TARGET" like the older ones did. ?Anyway, just
> having tried this, systemtap's autoconf stuff is not set up properly
> for this style of cross-compilation (it fails during one of the
> configure file-existence checks). ?It may not be a big job to fix it.
>
> In any case, you need far more than a cross gcc to make this work.
> You need a full toolchain including cross ld, cross glibc, and cross
> any other libraries that staprun may need to link to. ?(I'm assuming
> you'd only ever try the --disable-translator cross build.) ?And you'll
> need a cross-configured kernel build tree to build kernel modules
> against.
>
> You should consider building staprun natively on the arm box.
>
> - FChE
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]