From: "Roger.Gough" <Roger.Gough@ul.ie>
To: gcc-help@gcc.gnu.org
Subject: porting gcc version 2.72
Date: Wed, 29 Jan 2003 19:01:00 -0000 [thread overview]
Message-ID: <0B2F845E9599D611A6FA00B0D0D1DE4A277953@exch-staff4.ul.ie> (raw)
Hi All,
I am looking for some help in porting GCC version 2.7.2 to a dsp
processor. I have the necessary machine description files, i.e
dsp16xx.c,dsp16xx.h, and dsp16xx.md.
I start of in my source directory and do my configuration as
follows:
roger_gough@Craggy:~/gcc-2.7.2> ./configure --target=dsp16xx
This appears to be a i686-unknown-linux system.
Using `./config/dsp16xx/dsp16xx.c' to output insns.
Using `./config/dsp16xx/dsp16xx.md' as machine description file.
Using `./config/dsp16xx/dsp16xx.h' as target machine macro file.
Using `./config/i386/xm-linux.h' as host machine macro file.
Merged x-linux.
Merged c++ fragment(s).
Created `./Makefile'.
Merged x-linux.
Created `cp/Makefile'.
Links are now set up to build a cross-compiler for dsp16xx-unknown-none
from i686-unknown-linux.
The configuration seems to be ok. I then move into my object
directory which is a subdirectory of my source directory to try and build my
port:
roger_gough@Craggy:~/gcc-2.7.2> cd objc
roger_gough@Craggy:~/gcc-2.7.2/objc> make
However, at this point I get the following errors:
make[1]: *** [gcc.o] Error 1
make[1]: Leaving directory `/home/roger_gough/gcc-2.7.2'
make: *** [all] Error 2
1. Are these make errors problems with my code or do they arise because i am
attempting to build the port incorrectly?
2. Is it ok to have an object directory as a subdirectory of a source
directory as i did above?
3. I am using SuSe linux 8.0 which already has version GCC 3.2 running on
it. Should there be issues with trying to port GCC version 2.72?
I am new to GCC, which is probably obvious from above, but I would be very
grateful for any help. Thanks in advance.
Rgds
Roger.
next reply other threads:[~2003-01-29 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 19:01 Roger.Gough [this message]
[not found] <616BE6A276E3714788D2AC35C40CD18DA0BD60@whale.softwire.co.uk>
2003-01-30 9:27 ` Rupert Wood
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=0B2F845E9599D611A6FA00B0D0D1DE4A277953@exch-staff4.ul.ie \
--to=roger.gough@ul.ie \
--cc=gcc-help@gcc.gnu.org \
/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).