public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: gkosteva@comcast.net
To: systemtap@sourceware.org
Subject: Using the systemtap configure script on Ubuntu 9.04
Date: Tue, 18 May 2010 02:43:00 -0000	[thread overview]
Message-ID: <1403544278.21154761274107672524.JavaMail.root@sz0020a.westchester.pa.mail.comcast.net> (raw)
In-Reply-To: <134922441.21152901274107488199.JavaMail.root@sz0020a.westchester.pa.mail.comcast.net>


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.


 

  parent reply	other threads:[~2010-05-17 14:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <134922441.21152901274107488199.JavaMail.root@sz0020a.westchester.pa.mail.comcast.net>
2010-05-17 18:40 ` gkosteva
2010-05-18  2:44   ` Mark Wielaard
2010-05-18  3:16     ` Rayson Ho
2010-05-18  2:43 ` gkosteva [this message]
     [not found] <783052208.24376951274969900448.JavaMail.root@sz0020a.westchester.pa.mail.comcast.net>
2010-05-28 14:08 ` gkosteva
2010-05-28 21:12   ` Josh Stone
     [not found] <342948981.21681601274214320052.JavaMail.root@sz0020a.westchester.pa.mail.comcast.net>
2010-05-19 16:47 ` gkosteva
2010-05-20 19:32   ` Frank Ch. Eigler
     [not found] <772953842.21530011274192893348.JavaMail.root@sz0020a.westchester.pa.mail.comcast.net>
     [not found] ` <867844766.21531311274193047777.JavaMail.root@sz0020a.westchester.pa.mail.comcast.net>
2010-05-18 20:08   ` Rayson Ho
2010-05-12 16:16 gkosteva
2010-05-12 19:11 ` Frank Ch. Eigler
     [not found]   ` <1399661091.19844181273684891134.JavaMail.root@sz0020a.westchester.pa.mail.comcast.net>
2010-05-13 16:54     ` Frank Ch. Eigler

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=1403544278.21154761274107672524.JavaMail.root@sz0020a.westchester.pa.mail.comcast.net \
    --to=gkosteva@comcast.net \
    --cc=systemtap@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).