From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8873 invoked by alias); 26 Oct 2009 19:56:50 -0000 Received: (qmail 8865 invoked by uid 22791); 26 Oct 2009 19:56:50 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 26 Oct 2009 19:56:46 +0000 Received: from int-mx03.intmail.prod.int.phx2.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.16]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n9QJuiVI023748 for ; Mon, 26 Oct 2009 15:56:45 -0400 Received: from fche.csb (vpn-227-44.phx2.redhat.com [10.3.227.44]) by int-mx03.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id n9QJuibd031367; Mon, 26 Oct 2009 15:56:44 -0400 Received: by fche.csb (Postfix, from userid 2569) id A08C558118; Mon, 26 Oct 2009 15:56:43 -0400 (EDT) To: naresh kamboju Cc: systemtap@sources.redhat.com Subject: Re: systemTap 1.0 CROSS COMPILE References: From: fche@redhat.com (Frank Ch. Eigler) Date: Mon, 26 Oct 2009 19:56:00 -0000 In-Reply-To: (naresh kamboju's message of "Mon, 26 Oct 2009 23:02:15 +0530") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2009-q4/txt/msg00290.txt.bz2 naresh kamboju 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