hurd-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gcc/binutils porting


From: Mark Kettenis
Subject: Re: gcc/binutils porting
Date: Mon, 29 Oct 2001 09:41:42 +0100

   From: Roland McGrath <address@hidden>
   Date: Sun, 28 Oct 2001 21:49:20 -0500 (EST)

   What does it take to make binutils and gcc dtrt for a new CPU-gnu platform,
   when there is already a working ELF-based CPU-linux configuration?

It's basically a matter of changing a few configuration files.

   I'd like to get these changes in for powerpc-gnu before too long.  But I'd
   also like to have the procedure spelled out, at least in part, so that
   people embarking on new Hurd ports can tackle this part themselves early on.

How about this:

General
-------

Start working from the current development sources.  Worry about
getting your changes into a release branch later.


Binutils
--------

See http://sources.redhat.com/binutils how to get the current
development tree by anonymous CVS.  Send patches to
address@hidden

Filling in the missing bits in bfd/config.bfd, gas/configure.in and
ld/configure.tgt is probably enough.  Take the existing i386-*-gnu*
and *-*-linux-gnu* targets as a model.  Be careful to make sure that
*-*-gnu* comes after *-*-linux-gnu* to avoid breaking linux targets.

Since I have a bit of experience with adding new targets to binutils,
feel free to send any patches to me for review: address@hidden


GCC
---

See http://gcc.gnu.org for info.  There are detailed instructions for
contributing to GCC that can be found on that web page.  Send patches
to address@hidden

At minimum you should add the missing bits to gcc/config.gcc, and
create a gcc/config/CPU/gnu.h file to override a few Linux-specific
bits that are a bit different on the Hurd.

When the C compiler bootstraps, start worrying about libstdc++.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]