From: msarasa@fh-konstanz.de
To: gdb@sources.redhat.com
Subject: error building gcc , (simulators and targets...)
Date: Wed, 15 Jan 2003 10:13:00 -0000 [thread overview]
Message-ID: <1042625614.3e25344e7f05b@webmail.fh-konstanz.de> (raw)
I'm trying to build gcc for a specific target : m68k for example
as I do:
make all
I get this error message:
miguel@stefan:~/gcc_sim/build-binutils > make all
make all-recursive
make[1]: Entering directory `/home/miguel/gcc_sim/build-binutils'
Making all in doc
make[2]: Entering directory `/home/miguel/gcc_sim/build-binutils/doc'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/miguel/gcc_sim/build-binutils/doc'
Making all in po
make[2]: Entering directory `/home/miguel/gcc_sim/build-binutils/po'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/miguel/gcc_sim/build-binutils/po'
make[2]: Entering directory `/home/miguel/gcc_sim/build-binutils'
make[2]: *** No rule to make target `../bfd/bfd.h', needed by `size.o'. Stop.
make[2]: Leaving directory `/home/miguel/gcc_sim/build-binutils'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/miguel/gcc_sim/build-binutils'
make: *** [all-recursive-am] Error 2
What should I do? I'm really a begginer!
The goal of my efforts is to configure gdb to its use with a simulator, in
order to see what should I do to configure my own undefined simulator for a
new , not defined processor.
Any ideas would be really wellcomed
What could I read? Or analyze?
Thank you very much.
Miguel
next reply other threads:[~2003-01-15 10:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 10:13 msarasa [this message]
2003-01-15 13:21 ` Daniel Jacobowitz
2003-01-15 16:13 ` Andrew Cagney
2003-01-15 16:15 ` Daniel Jacobowitz
2003-01-15 16:48 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 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
2003-01-16 17:02 Michael Elizabeth Chastain
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=1042625614.3e25344e7f05b@webmail.fh-konstanz.de \
--to=msarasa@fh-konstanz.de \
--cc=gdb@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