From: msarasa@fh-konstanz.de
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Michael Elizabeth Chastain <mec@shout.net>,
ac131313@redhat.com, gdb@sources.redhat.com
Subject: Re: error building gcc , (simulators and targets...)
Date: Thu, 16 Jan 2003 15:20:00 -0000 [thread overview]
Message-ID: <1042730430.3e26cdbe2e714@webmail.fh-konstanz.de> (raw)
In-Reply-To: <20030116143123.GA22476@nevyn.them.org>
Zitat von Daniel Jacobowitz <drow@mvista.com>:
> On Thu, Jan 16, 2003 at 03:18:15PM +0100, msarasa@fh-konstanz.de wrote:
> > Zitat von Daniel Jacobowitz <drow@mvista.com>:
> >
> > > On Thu, Jan 16, 2003 at 01:55:02PM +0100, msarasa@fh-konstanz.de wrote:
> > > > I made four directories for building Binutils , GCC , Newlib and Gdb ,
> in
> > > this
> > > > order.
> > > > They're called:
> > > > build-gcc
> > > > build-binutils
> > > > build-newlib
> > > > build-gdb
> > > >
> > > > I made also a folder h8300-elf-gnu to install there.
> > > >
> > > > Sources are contained in miguel/gnu
> > > >
> > > > I made
> > > > cd build-newlib
> > > > ../gnu/binutils/configure --prefix=/h8300-elf-gnu --target=h8300-elf
> > > >
> > > > There's no error message with this , but then I do
> > >
> > > Same problem. Try
> > >
> > > ../gnu/configure --prefix=/h8300-elf-gnu --target=h8300-elf
> > >
> >
> > this wouldn't configure not only binutils but the whole gnu? I've made that
> ,
> > and seems like the configuration for all the stuff...
> > Or , should I do this instead of one configure than one make for binutils ,
>
> > that for gcc... Is this the way to configure and Install gnu in one step?
>
> Yes, you configure everything at once. Then you can just say "make".
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
>
I've just made that , but:
I didn't get an executable looking like h8300-elf-gdb
I ran gdb, but I still have no success with "target sim" command , even though
this processor should have a built-in simulator.
Thanks again!
next prev parent reply other threads:[~2003-01-16 15:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 17:13 Michael Elizabeth Chastain
2003-01-16 9:58 ` msarasa
2003-01-16 12:54 ` msarasa
2003-01-16 13:50 ` Daniel Jacobowitz
2003-01-16 14:18 ` msarasa
2003-01-16 14:31 ` Daniel Jacobowitz
2003-01-16 15:20 ` msarasa [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-16 17:02 Michael Elizabeth Chastain
2003-01-15 16:50 Daniel Jacobowitz
2003-01-15 16:50 Michael Elizabeth Chastain
2003-01-15 16:59 ` Andrew Cagney
2003-01-15 17:11 ` msarasa
2003-01-15 16:48 Michael Elizabeth Chastain
2003-01-15 10:13 msarasa
2003-01-15 13:21 ` Daniel Jacobowitz
2003-01-15 16:13 ` Andrew Cagney
2003-01-15 16:15 ` Daniel Jacobowitz
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=1042730430.3e26cdbe2e714@webmail.fh-konstanz.de \
--to=msarasa@fh-konstanz.de \
--cc=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=mec@shout.net \
/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