Re: Using the systemtap configure script on Ubuntu 9.04

Re: Using the systemtap configure script on Ubuntu 9.04

[gkosteva]

Frank, a little elaboration here would be helpful!  You write:

"stap needs to be natively compiled on the development host where the arm
platform's kernel etc. were built."

This step is not described in http://omappedia.org/wiki/Systemtap at least its not obvious to me what the step is to compile stap.
Can someone take the time to describe this. Otherwise I am soon going to bail on using this tool. I have oprofile already working. The install of this tool and any support for it have just been rather painful. To be honest, I don't even know if the effort is worth while. I am trying to verify the performance of my system and this tool was recommended by Steve Dickson and for all I know this tool may be a piece of junk....if the install is any indication, I am not hopeful.

Thanks.



----- Original Message -----
From: "Frank Ch. Eigler" <fche@redhat.com>
To: gkosteva@comcast.net
Cc: "Rayson Ho" <raysonlogin@gmail.com>, systemtap@sourceware.org
Sent: Thursday, May 20, 2010 10:57:11 AM GMT -05:00 US/Canada Eastern
Subject: Re: Using the systemtap configure script on Ubuntu 9.04

gkosteva@comcast.net writes:

> I got the configure to work and ran the make install which successfully
> created the target bound /systemtap-1.0-macharm directory.=20
> I am now trying to generate the *.ko file using the command:
>
> ./stap -gv -a arm -D OMAP_REL_FAMILY -B CROSS_COMPILE=arm-none-linux-gnueabi- -r .....

> However, my /systemtap-1.0-macharm/bin directory only contains stap-report
> and staprun, but no stap executable/script to generate the required .ko file

It looks like the wrong parts of the tool were built.  staprun needs
to be cross-compiled or natively compiled for the arm platform.  stap
needs to be natively compiled on the development host where the arm
platform's kernel etc. were built.

- FChE

Re: Using the systemtap configure script on Ubuntu 9.04

[Josh Stone]

On 05/27/2010 07:19 AM, gkosteva@comcast.net wrote:
> Frank, a little elaboration here would be helpful!  You write:
> 
> "stap needs to be natively compiled on the development host where the arm
> platform's kernel etc. were built."

There are two components to consider for systemtap.

The runtime, with bin/staprun and libexec/systemtap/stapio, needs to be
built as native arm executables for the target machine.  It sounds like
you've accomplished this already.

The translator, with bin/stap and share/systemtap/* and all, needs to
run in an environment that is able to build the kernel and kernel
modules for the arm target.  Since the development host is usually some
other architecture, probably x86, then the stap binary needs to be built
for x86 and then used with -a and -B to cross-compile.

So, you'll need two separate configure+builds, once to get the runtime
for arm, and once to get the translator for the development host.

> This step is not described in http://omappedia.org/wiki/Systemtap at
> least its not obvious to me what the step is to compile stap.

I hope my description helps you understand how the pieces need to fit
together.

Cross-compilation hasn't seen much focus from our core development team
-- the page you're referencing was written by the OMAP folks.  It's a
wiki, so I'm sure the authors would welcome your help in clarifying the
instructions.  We would also welcome help to improve the core
documentation in this respect.

Thanks,

Josh

Re: Using the systemtap configure script on Ubuntu 9.04

[Frank Ch. Eigler]

gkosteva@comcast.net writes:

> I got the configure to work and ran the make install which successfully
> created the target bound /systemtap-1.0-macharm directory.=20
> I am now trying to generate the *.ko file using the command:
>
> ./stap -gv -a arm -D OMAP_REL_FAMILY -B CROSS_COMPILE=arm-none-linux-gnueabi- -r .....

> However, my /systemtap-1.0-macharm/bin directory only contains stap-report
> and staprun, but no stap executable/script to generate the required .ko file

It looks like the wrong parts of the tool were built.  staprun needs
to be cross-compiled or natively compiled for the arm platform.  stap
needs to be natively compiled on the development host where the arm
platform's kernel etc. were built.

- FChE

Re: Using the systemtap configure script on Ubuntu 9.04

[gkosteva]

Hi,

I got the configure to work and ran the make install which successfully
created the target bound /systemtap-1.0-macharm directory. 
I am now trying to generate the *.ko file using the command:
./stap -gv -a arm -D OMAP_REL_FAMILY -B CROSS_COMPILE=arm-none-linux-gnueabi- -r .....

However, my /systemtap-1.0-macharm/bin directory only contains stap-report and staprun,
but no stap executable/script to generate the required .ko file

Any Ideas?
Thanks Glenn.



----- Original Message -----
From: "Rayson Ho" <raysonlogin@gmail.com>
To: gkosteva@comcast.net
Cc: systemtap@sourceware.org
Sent: Tuesday, May 18, 2010 11:56:40 AM GMT -05:00 US/Canada Eastern
Subject: Re: Using the systemtap configure script on Ubuntu 9.04

On Tue, May 18, 2010 at 9:30 AM wrote:
> Hi Rayson,
> Well I got a little further !!!  (thanks for the info)

Great!

And looks like you didn't cc the list, so Glenn & others didn't get the message.

> I extracted elfutils to /elfutils-0.146 and then
> I ran the commands below and now get a different set of errors:
>
> I have attached the config.log file which contains the following errors:
>
> configure:4245: gcc -E  conftest.c
> conftest.c:10:28: error: ac_nonexistent.h: No such file or directory
> configure: failed program was:
> | /* confdefs.h.  */
> conftest.c:10:28: error: ac_nonexistent.h: No such file or directory
>
> configure:7023: checking for /usr/include/nss3
> configure:7029: error: cannot check for file existence when cross compiling


The first few errors related to "No such file or directory" should be
OK -- as long as configure was not stopped by them. Configure needs to
do a lot of trial and error compilations to test the configurations of
the compile environment.

The real concern is "cannot check for file existence when cross
compiling", but if you google that message (a trick that is always
useful -- grab the error message and google it!), you will find that
it is a very common problem in cross compile environments. Some people
fix this by commenting out the check, or provide the value in the
config.cache file.

If you open the configure script in a text editor, you can do a bit of
hacking to customize it for your cross-compile environment.

Rayson


> Also the console output is below
> Thanks for your help, Glenn.
>
> ------------------------------------------
> LTIB> ac_cv_file__usr_include_nspr=no
> LTIB> ac_cv_file__usr_include_nspr4=no
> LTIB> ac_cv_file__usr_include_nss=no
> LTIB> ac_cv_file__usr_include_nss3=no
> LTIB> ac_cv_func_malloc_0_nonnull=yes
> LTIB> ./configure --exec-prefix=/systemtap-1.2-macharm --prefix=/systemtap-1.2-macharm --host=arm-none-linux-gnueabi CXXFLAGS=-static CFLAGS=-static --disable-translator --disable-docs --disable-refdocs --disable-grapher --without-rpm --with-elfutils=/elfutils-0.146
>
>
> configure: WARNING: If you wanted to set the --build type, don't use --host.
>    If a cross compiler is detected then cross compile mode will be used.
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for arm-none-linux-gnueabi-strip... arm-none-linux-gnueabi-strip
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking whether ln -s works... yes
> checking for arm-none-linux-gnueabi-gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... yes
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking how to run the C preprocessor... gcc -E
> checking for arm-none-linux-gnueabi-gcc... (cached) gcc
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for gcc option to accept ISO C89... (cached) none needed
> checking dependency style of gcc... (cached) gcc3
> checking whether gcc and cc understand -c and -o together... yes
> checking for function prototypes... yes
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for string.h... (cached) yes
> checking for arm-none-linux-gnueabi-ranlib... arm-none-linux-gnueabi-ranlib
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether make sets $(MAKE)... (cached) yes
> checking to see if prologue searching should be the default... no
> configure: Compiling with gcc -fstack-protector-all et al.
> checking for sqlite3_open in -lsqlite3... no
> checking for latex... no
> checking for dvips... no
> checking for ps2pdf... yes
> checking for latex2html... no
> checking for publican... no
> checking for xmlto... no
> checking for certutil... no
> checking for /usr/include/nss3... configure: error: cannot check for file existence when cross compiling
> ----------------------------------------------------------------------------------------------------------
>
>

Re: Using the systemtap configure script on Ubuntu 9.04

[Rayson Ho]

On Tue, May 18, 2010 at 9:30 AM wrote:
> Hi Rayson,
> Well I got a little further !!!  (thanks for the info)

Great!

And looks like you didn't cc the list, so Glenn & others didn't get the message.

> I extracted elfutils to /elfutils-0.146 and then
> I ran the commands below and now get a different set of errors:
>
> I have attached the config.log file which contains the following errors:
>
> configure:4245: gcc -E  conftest.c
> conftest.c:10:28: error: ac_nonexistent.h: No such file or directory
> configure: failed program was:
> | /* confdefs.h.  */
> conftest.c:10:28: error: ac_nonexistent.h: No such file or directory
>
> configure:7023: checking for /usr/include/nss3
> configure:7029: error: cannot check for file existence when cross compiling


The first few errors related to "No such file or directory" should be
OK -- as long as configure was not stopped by them. Configure needs to
do a lot of trial and error compilations to test the configurations of
the compile environment.

The real concern is "cannot check for file existence when cross
compiling", but if you google that message (a trick that is always
useful -- grab the error message and google it!), you will find that
it is a very common problem in cross compile environments. Some people
fix this by commenting out the check, or provide the value in the
config.cache file.

If you open the configure script in a text editor, you can do a bit of
hacking to customize it for your cross-compile environment.

Rayson


> Also the console output is below
> Thanks for your help, Glenn.
>
> ------------------------------------------
> LTIB> ac_cv_file__usr_include_nspr=no
> LTIB> ac_cv_file__usr_include_nspr4=no
> LTIB> ac_cv_file__usr_include_nss=no
> LTIB> ac_cv_file__usr_include_nss3=no
> LTIB> ac_cv_func_malloc_0_nonnull=yes
> LTIB> ./configure --exec-prefix=/systemtap-1.2-macharm --prefix=/systemtap-1.2-macharm --host=arm-none-linux-gnueabi CXXFLAGS=-static CFLAGS=-static --disable-translator --disable-docs --disable-refdocs --disable-grapher --without-rpm --with-elfutils=/elfutils-0.146
>
>
> configure: WARNING: If you wanted to set the --build type, don't use --host.
>    If a cross compiler is detected then cross compile mode will be used.
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for arm-none-linux-gnueabi-strip... arm-none-linux-gnueabi-strip
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking whether ln -s works... yes
> checking for arm-none-linux-gnueabi-gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... yes
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking how to run the C preprocessor... gcc -E
> checking for arm-none-linux-gnueabi-gcc... (cached) gcc
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for gcc option to accept ISO C89... (cached) none needed
> checking dependency style of gcc... (cached) gcc3
> checking whether gcc and cc understand -c and -o together... yes
> checking for function prototypes... yes
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for string.h... (cached) yes
> checking for arm-none-linux-gnueabi-ranlib... arm-none-linux-gnueabi-ranlib
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether make sets $(MAKE)... (cached) yes
> checking to see if prologue searching should be the default... no
> configure: Compiling with gcc -fstack-protector-all et al.
> checking for sqlite3_open in -lsqlite3... no
> checking for latex... no
> checking for dvips... no
> checking for ps2pdf... yes
> checking for latex2html... no
> checking for publican... no
> checking for xmlto... no
> checking for certutil... no
> checking for /usr/include/nss3... configure: error: cannot check for file existence when cross compiling
> ----------------------------------------------------------------------------------------------------------
>
>

Re: Using the systemtap configure script on Ubuntu 9.04

[Rayson Ho]

Gkosteva,

The error message shows that configure was trying to run "a.out" it
compiled with the arm-none-linux-gnueabi-gcc cross-compiler in the
compile environment, and since it's an x86 box, the binary failed to
run.

The wiki has some info on cross compilation, and it also lists the
extra configure flags needed for the cross environment. However I
usually don't deal with cross environments, so you will need to do a
bit of trial and error to get it working.

Rayson



On Mon, May 17, 2010 at 10:30 AM, Mark Wielaard <mjw@redhat.com> wrote:
> On Mon, 2010-05-17 at 14:47 +0000, gkosteva@comcast.net wrote:
>>     "In order to compile the tool and scripts, elfutils package shall be available on the host.
>>     elfutils 0.143 package can be downloaded from following location [5]
>>     No need to install elfutils on the host; only the untar'ed file is required."
>>
>>    so is elfutils required?  line 1 says yes, line 3 says no ???
>
> You don't have to install it, systemtap can use the sources to build and
> link against itself when configure is given the
> --with-elfutils=/path/to/elfutils-sources option.
>>
>>  From my compile environment on the PC, I attempt to run ./configure to generate
>>  the proper make files and get the following error message:
>>
>> -----------------------------------------------------------------
>> [IMX BUILD]> cd systemtap-1.2/
>> [IMX BUILD]> ./configure
>> checking for a BSD-compatible install... /usr/bin/install -c
>> checking whether build environment is sane... yes
>> checking for a thread-safe mkdir -p... /bin/mkdir -p
>> checking for gawk... no
>> checking for mawk... mawk
>> checking whether make sets $(MAKE)... yes
>> checking whether to enable maintainer-specific portions of Makefiles... no
>> checking whether ln -s works... yes
>> checking for gcc... arm-none-linux-gnueabi-gcc
>> checking for C compiler default output file name... a.out
>> checking whether the C compiler works... configure: error: in `/home/gkosteva/SVN_trunk/embedded/celiav1/imx31/stage/systemtap-1.2':
>> configure: error: cannot run C compiled programs.
>> If you meant to cross compile, use `--host'.
>> See `config.log' for more details.
>> [IMX BUILD]>
>> ---------------------------------------------------------------------
>>
>> Any ideas how/why the configure script is not working?
>
> Look in config.log for more details.
> I assume you are trying to cross-compile and something in your toolchain
> isn't setup correctly. config.log will tell you what.
>
> It might be easier to build and run systemtap on the arm box directly.
>
> Cheers,
>
> Mark
>
>

Re: Using the systemtap configure script on Ubuntu 9.04

[Mark Wielaard]

On Mon, 2010-05-17 at 14:47 +0000, gkosteva@comcast.net wrote:
>     "In order to compile the tool and scripts, elfutils package shall be available on the host. 
>     elfutils 0.143 package can be downloaded from following location [5] 
>     No need to install elfutils on the host; only the untar'ed file is required."
> 
>    so is elfutils required?  line 1 says yes, line 3 says no ???

You don't have to install it, systemtap can use the sources to build and
link against itself when configure is given the
--with-elfutils=/path/to/elfutils-sources option.
> 
>  From my compile environment on the PC, I attempt to run ./configure to generate
>  the proper make files and get the following error message:
> 
> -----------------------------------------------------------------
> [IMX BUILD]> cd systemtap-1.2/
> [IMX BUILD]> ./configure
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking whether ln -s works... yes
> checking for gcc... arm-none-linux-gnueabi-gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... configure: error: in `/home/gkosteva/SVN_trunk/embedded/celiav1/imx31/stage/systemtap-1.2':
> configure: error: cannot run C compiled programs.
> If you meant to cross compile, use `--host'.
> See `config.log' for more details.
> [IMX BUILD]>
> ---------------------------------------------------------------------
> 
> Any ideas how/why the configure script is not working?

Look in config.log for more details.
I assume you are trying to cross-compile and something in your toolchain
isn't setup correctly. config.log will tell you what.

It might be easier to build and run systemtap on the arm box directly.

Cheers,

Mark

Using the systemtap configure script on Ubuntu 9.04

[gkosteva]

Hello,

   I am running Ubuntu 9.04 on my PC which is running the LTIB software that
 generates ARM code for our embedded system. I have modified our kernel with 
 the right configurations for systemtap. I now need to compile the systemtap 
 application on my PC, then port to the embedded ARM using a serial port consol.

 I am following the directions on the site: http://omappedia.org/wiki/Systemtap
 From my compile environment on the PC, I attempt to run ./configure to generate
 the proper make files and get the following error message:

-----------------------------------------------------------------
[IMX BUILD]> cd systemtap-1.2/
[IMX BUILD]> ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether ln -s works... yes
checking for gcc... arm-none-linux-gnueabi-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: in `/home/gkosteva/SVN_trunk/embedded/celiav1/imx31/stage/systemtap-1.2':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
[IMX BUILD]>
---------------------------------------------------------------------

Any ideas how/why the configure script is not working?
Thanks.


 

Using the systemtap configure script on Ubuntu 9.04

[gkosteva]

Hello,

   I am running Ubuntu 9.04 on my PC which is running the LTIB software that
 generates ARM code for our embedded system. I have modified our kernel with 
 the right configurations for systemtap. I now need to compile the systemtap 
 application on my PC, then port to the embedded ARM using a serial port consol.

 I am following the directions on the site: http://omappedia.org/wiki/Systemtap
 this web site says:

    "In order to compile the tool and scripts, elfutils package shall be available on the host. 
    elfutils 0.143 package can be downloaded from following location [5] 
    No need to install elfutils on the host; only the untar'ed file is required."

   so is elfutils required?  line 1 says yes, line 3 says no ???


 From my compile environment on the PC, I attempt to run ./configure to generate
 the proper make files and get the following error message:

-----------------------------------------------------------------
[IMX BUILD]> cd systemtap-1.2/
[IMX BUILD]> ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether ln -s works... yes
checking for gcc... arm-none-linux-gnueabi-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: in `/home/gkosteva/SVN_trunk/embedded/celiav1/imx31/stage/systemtap-1.2':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
[IMX BUILD]>
---------------------------------------------------------------------

Any ideas how/why the configure script is not working?
Thanks.


 

Re: Using the systemtap configure script on Ubuntu 9.04

[Frank Ch. Eigler]

Hi -

On Wed, May 12, 2010 at 05:21:31PM +0000, gkosteva@comcast.net wrote:
> [...]
> What I need:
>   I am running Ubuntu 9.04 on my PC which is running the LTIB software that 
> generates ARM code for our embedded system. What I would like to do is 
> modify our kernel with the right configurations for systemtap (done this) 
> and then compile the systemtap application to run on the ARM using the 
> serial port consol for communication.

> The omapmedia site seems to describe a server/client approach which won't 
> work for me. (Our imx31 has no client connection capability)

OK, that just means that the automated client/server widget can't be
used, but you can still build the various parts of systemtap the same
way.  Instead of running stap-client on the arm machine and
stap-server on the development host, you'd run 'stap -p4 ....' on the
host by hand, transport the foo.ko file to the arm machine any way you
see fit, and run it there with 'staprun foo.ko'.

(If the arm machine has enough ram/virtual memory, building/running
all of systemtap natively is also a possibility.)

- FChE

Re: Using the systemtap configure script on Ubuntu 9.04

[Frank Ch. Eigler]

gkosteva@comcast.net writes:

> I am trying to build systemtap for the freescale imx31 (arm)
> processor.  [...]  Should I be using a different process to create
> my systemtap executable for the imx31?

You need to decide whether you wish to undertake a native or
cross-compilation effort.  The simplest method is running gcc,
systemtap, and everything on the arm box.  Cross-compilation can be
done in one or two different ways in theory, but the one that works
smoother is natively building systemtap-runtime only, and
building/running the translator side (stap) on some host machine.

See also http://sourceware.org/ml/systemtap/2010-q1/msg00671.html
See also http://omappedia.org/wiki/Systemtap

- FChE

Using the systemtap configure script on Ubuntu 9.04

[gkosteva]

Hello,
I am trying to build systemtap for the freescale imx31 (arm) processor.
I have successfully updated my kernel build with CONFIG_RELAY, CONFIG_DEBUG_FS, CONFIG_KPROBES, and CONFIG_DEBUG INFO.
 
I downloaded systemtap-1.2.tar.gz from the sourceware.org website.
From my compile environment I attempted to run the systemtap configure script and got the output below.
It suggested that I cross compile using the --host option, but help does not provide info on this particular option.
Should I be using a different process to create my systemtap executable for the imx31?
 
Thanks.
-----------------------------------------------------------------
[IMX BUILD]> cd systemtap-1.2/
[IMX BUILD]> ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether ln -s works... yes
checking for gcc... arm-none-linux-gnueabi-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: in `/home/gkosteva/SVN_trunk/embedded/celiav1/imx31/stage/systemtap-1.2':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
[IMX BUILD]> 
---------------------------------------------------------------------