This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: systemTap 1.0 CROSS COMPILE
Hi,
If any body compiled on PPC (PowerPC) please share the step to cross compile.
Best regards,
Naresh Kamboju
On Tue, Oct 27, 2009 at 1:26 AM, Frank Ch. Eigler <fche@redhat.com> wrote:
> naresh kamboju <naresh.kernel@gmail.com> writes:
>
>> [...] ?I have to build and install stap and staprun binaries on the
>> Host Machine by using cross compilation. ?I'll use stap to build .ko
>> files and copy on the target arm architecture board and insert and
>> execute the module with staprun. [...]
>
> OK. ?Recall that systemtap is itself a translator/compiler, so in fact
> we have several possible "crossings":
>
> 1) the machine where systemtap itself is compiled
> 2) the machine where systemtap is *run*, to translate scripts to .ko's
> 3) the machine where the modules are run via staprun
>
> The recent cross-architecture enhancements were for the 2->3 crossing,
> so wherevever systemtap was run, it could create output .ko's for a
> different architecture.
>
> We have not tried to do 1->2 (for stap) or 1->3 (for staprun) itself,
> so that we have been expecting systemtap itself (or at least staprun)
> to be built natively (on your ARM machine).
>
> OTOH it should be possible to cross-compile systemtap (or at least
> staprun).
>
>> 7. ./configure --host=i686-pc-linux-gnueabi --prefix=/usr/local/arm/
>> --with-elfutils=elfutils...
>
> Try instead
>
> .../configure --target=arm... --prefix=... --with-elfutils=... --disable-translator
>
>
> - FChE
>