public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Backhaus Willy" <w.backhaus@newage-avkseg.com>
To: <insight@sources.redhat.com>
Subject: Insight build error
Date: Wed, 08 Dec 2004 12:10:00 -0000	[thread overview]
Message-ID: <000001c4dd1e$e7029500$f30210ac@backhaus> (raw)

hello,

I'm trying to build Insight from cvs.
following error message comes:

/bin/gcc -c
/ecos-c/gnutools/src/insight_cvs/src/sim/arm/../common/run.c -DHAVE_CONFIG_H
     -DPROFILE=1 -DWITH_PROFILE=-1          -DDEFAULT_INLINE=0           -DM
ODET -DNEED_UI_LOOP_HOOK -DSIM_TARGET_SWITCHES   -I. -I/ecos-c/gnutools/src/
insight_cvs/src/sim/arm -I../common -I/ecos-c/gnutools/src/insight_cvs/src/s
im/arm/../common -I../../include -I/ecos-c/gnutools/src/insight_cvs/src/sim/
arm/../../include -I../../bfd -I/ecos-c/gnutools/src/insight_cvs/src/sim/arm
/../../bfd -I../../opcodes -I/ecos-c/gnutools/src/insight_cvs/src/sim/arm/..
/../opcodes -I../../intl -I/ecos-c/gnutools/src/insight_cvs/src/sim/arm/../.
./intl -g -O2
make[2]: *** No rule to make target `../../intl/libintl.a', needed by `run'.
Stop.
make[2]: Leaving directory `/ecos-c/gnutools/tmp/build/gdb/sim/arm'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/ecos-c/gnutools/tmp/build/gdb/sim'
make: *** [all-sim] Error 2
make: Leaving directory `/ecos-c/gnutools/tmp/build/gdb'

I use cygwin and Win2000.

any ideas?

thanks.

Willy

             reply	other threads:[~2004-12-08 12:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08 12:10 Backhaus Willy [this message]
2004-12-08 12:23 ` Dave Korn
2004-12-08 15:14   ` Backhaus Willy
2004-12-08 18:27     ` Keith Seitz
2004-12-14 17:54       ` Insight build error - success Backhaus Willy
2004-12-14 18:18         ` Keith Seitz
2005-05-02 13:16 Insight build error neuwald
2005-05-02 13:51 ` Fernando Nasser

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='000001c4dd1e$e7029500$f30210ac@backhaus' \
    --to=w.backhaus@newage-avkseg.com \
    --cc=insight@sources.redhat.com \
    /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).