From: "Rupert Wood" <me@rupey.net>
To: "'Roger.Gough'" <Roger.Gough@ul.ie>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: porting gcc version 2.72
Date: Thu, 30 Jan 2003 09:27:00 -0000 [thread overview]
Message-ID: <616BE6A276E3714788D2AC35C40CD18D561862@whale.softwire.co.uk> (raw)
In-Reply-To: <616BE6A276E3714788D2AC35C40CD18DA0BD60@whale.softwire.co.uk>
Roger Gough wrote:
> 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.
Sorry to ask but: why do you want to start with GCC 2.7.2 rather than
the latest version? You'll likely get better support from GCC developers
working with a later version since they'll be more familiar with the
code, plus there are years of bug fixes, extra optimisations, etc. since
2.7.2.
> 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?
It's a compilation error in gcc.o; make is aborting because the GCC
building gcc.o exited with an error. You'll have to show us a few more
lines up.
> 2. Is it ok to have an object directory as a subdirectory of a source
> directory as i did above?
I don't think it's recommended but there's no good reason it shouldn't
work. On the other hand, it's easy for you to put the object directory
elsewhere.
> 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?
In theory, no. In practise, maybe - there might be problems compiling
very old codebases with newer GCCs. In particular, newer GCCs make
aliasing assumptions allowed by recent C standards; you might want to
look up the -f options for aliasing if you're having problems.
Good luck,
Rup.
next parent reply other threads:[~2003-01-30 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <616BE6A276E3714788D2AC35C40CD18DA0BD60@whale.softwire.co.uk>
2003-01-30 9:27 ` Rupert Wood [this message]
2003-01-29 19:01 Roger.Gough
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=616BE6A276E3714788D2AC35C40CD18D561862@whale.softwire.co.uk \
--to=me@rupey.net \
--cc=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).