From: "Andy Hare" <ahare@btinternet.com>
To: <morten.larsen@acte.no>
Cc: "Insight Mail list" <insight@sourceware.cygnus.com>
Subject: Re: configuring for arm-elf-gdb
Date: Mon, 13 Mar 2000 15:00:00 -0000 [thread overview]
Message-ID: <001201bf8d40$0fe9b0e0$0100000a@dualbeast> (raw)
In-Reply-To: <00Mar13.150648cet.115201@blue.acte.no>
Morten,
If you visit my Web Site at http://www.ahare.btinternet.co.uk you will
find my versions of the ATMEL AT91 library converted to using the GNU
Toolset. You will also find a copy of the toolset binaries that I am using
under NT. All these are in the download section
Andy Hare
----- Original Message -----
From: <morten.larsen@acte.no>
To: <ahare@btinternet.com>
Cc: <insight@sourceware.cygnus.com>
Sent: Monday, March 13, 2000 2:06 PM
Subject: RE: configuring for arm-elf-gdb
> Hi,
>
> as I am fairly new to (cross)GCC and GDB/Insight (using ARM's SDT
> previously),
> I wonder if you have examples of the following:
>
> 1) Makefile for build&install of the board support routines supplied by
> Atmel
> (unless you use your own ...)
>
> 2) Linker script for linking the support library (from 1)) w. user
program.
>
> Even a fragment or skeleton of any of these would help ...
> (besides, can GCC be instructed to generate Thumb-specific code?)
>
> -Thanks
>
> Rgds:
> Morten Larsen,
> ACTE Norway AS
>
> -----Original Message-----
> From: Andy Hare [ mailto:ahare@btinternet.com ]
> Sent: Monday, March 06, 2000 11:05 PM
> To: javelina
> Cc: Insight Mail list
> Subject: Re: configuring for arm-elf-gdb
>
>
> 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
> >
> >
>
next prev parent reply other threads:[~2000-03-13 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-13 6:11 morten.larsen
2000-03-13 15:00 ` Andy Hare [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-03-15 11:29 morten.larsen
2000-03-05 13:15 javelina
2000-03-06 14:09 ` Andy Hare
2000-03-06 15:01 ` Louis LeGrand
2000-03-06 16:39 ` Fernando Nasser
2000-03-06 19:29 ` javelina
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='001201bf8d40$0fe9b0e0$0100000a@dualbeast' \
--to=ahare@btinternet.com \
--cc=insight@sourceware.cygnus.com \
--cc=morten.larsen@acte.no \
/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).