From: "Rupert Wood" <me@rupey.net>
To: <shripada@india.hp.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: gcc porting
Date: Thu, 09 May 2002 05:27:00 -0000 [thread overview]
Message-ID: <616BE6A276E3714788D2AC35C40CD18D56168B@whale.softwire.co.uk> (raw)
In-Reply-To: <616BE6A276E3714788D2AC35C40CD18D621AFC@whale.softwire.co.uk>
Shripada wrote:
> well i am trying to configure gcc to produce code for a mc68000
> machine on my intel machine. The target is a posterminal... with a
> os called verix ( unix type) os.. I am trying to configure gcc ...
> so that it generates the object code which can be linked and the
> executable loaded on to the pop terminal The pos terminal has a
> mc68k processor... i hope i am clear now..
The GNU config.* haven't heard of verix.
You can build OS-neutral cross compilers which just target a specific
object format, e.g. m68k-elf or m68k-coff; probably your best bet would
be to find out which object format verix uses and then build a
cross-toolchain to target that. If you have system headers and C
libraries for verix then you should configure --without-newlib and drop
those into the build.
If you don't have system headers and libraries then you can use newlib
instead but you might have difficulty interacting with the system.
Good luck,
Rup.
next parent reply other threads:[~2002-05-09 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <616BE6A276E3714788D2AC35C40CD18D621AFC@whale.softwire.co.uk>
2002-05-09 5:27 ` Rupert Wood [this message]
2002-11-16 7:42 Gcc porting Alexander Shkurko
-- strict thread matches above, loose matches on Subject: below --
2002-05-09 5:16 gcc porting Shripad
2002-05-08 20:56 Shripad
2002-05-09 3:36 ` Raghavendra Koushik
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=616BE6A276E3714788D2AC35C40CD18D56168B@whale.softwire.co.uk \
--to=me@rupey.net \
--cc=gcc-help@gcc.gnu.org \
--cc=shripada@india.hp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).