public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Louis LeGrand <javelina@home.com>
To: insight@sourceware.cygnus.com
Subject: Re: configuring for arm-elf-gdb
Date: Mon, 06 Mar 2000 15:01:00 -0000	[thread overview]
Message-ID: <38C4389F.8A21ED09@home.com> (raw)
In-Reply-To: <05c801bf87b8$a75ebfc0$0100000a@dualbeast>

Andy and others,

Thanks for responding to my question.

Since my last message, I have sucessfuly built and installed arm-elf-gdb.  It
seems to work perfectly when run in the non-GUI mode (i.e. using the -nw
option).  However, when I run it in the GUI mode, the printf's output does not
show up anywhere.  I am using Redhat 6.1 not NT.  Do you have this problem?
The January 10, 2000 message from Kai Ruottu alludes to similar output issues.
I am not sure if I am doing something wrong, or if not seeing output is a known
"feature" of the code.

Thanks again,
L3

Andy Hare wrote:

> Hi
>
>     I have been building Insight-GDB under cygnus b20.1 under NT. Below is
> the following rules extracted from a makefile that I use to build all the
> GNU toolset.
>
> .PHONY: config-insight
> config-insight:
>  cd /c/cygnus/build/insight ; \
>  rm * -r ; \
>  /c/cygnus/GNU-Source-Code/insight/configure -v \
>   --prefix=/c/cygnus/xgcc-arm/insight \
>   --exec-prefix=/c/cygnus/xgcc-arm/insight \
>   --host=i586-cygwin32 --target=arm-elf >configure.out
>
> .PHONY: clean-insight
> clean-insight:
>  cd /c/cygnus/build/insight ; \
>  make clean
>
> .PHONY: insight
> insight:
>  cd /c/cygnus/build/insight ; \
>  make -w all install LIBGCC2_DEBUG_CFLAGS="-g1 -O1"  LANGUAGES="c c++" >
> make.out 2>&1
>
> These allow me to configure and build the Insight system, I have been using
> it both in the simulator mode and to connect to the ATMEL EB01 eval. board.
>
> Andy Hare
>
> ----- Original Message -----
> From: javelina <javelina@home.com>
> To: <insight@sourceware.cygnus.com>
> Sent: Sunday, March 05, 2000 9:14 PM
> Subject: configuring for arm-elf-gdb
>
> > Greetings,
> >
> > I am an ecos user and I would like to use the insight package to do GUI
> > remote debugging on an ARM evaluation board.  Looking at the mailing
> > list archive, it appears that others have done this, but it is not clear
> > to me what the steps are to build "arm-elf-gdb" instead of "gdb".
> >
> > Thanks,
> > L3
> >
> >

  reply	other threads:[~2000-03-06 15:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-05 13:15 javelina
2000-03-06 14:09 ` Andy Hare
2000-03-06 15:01   ` Louis LeGrand [this message]
2000-03-06 16:39     ` Fernando Nasser
2000-03-06 19:29       ` javelina
2000-03-13  6:11 morten.larsen
2000-03-13 15:00 ` Andy Hare
2000-03-15 11:29 morten.larsen

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=38C4389F.8A21ED09@home.com \
    --to=javelina@home.com \
    --cc=insight@sourceware.cygnus.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).