From owner-freebsd-alpha Tue Jul 22 14:41:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA00694 for alpha-outgoing; Tue, 22 Jul 1997 14:41:38 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA00687 for ; Tue, 22 Jul 1997 14:41:35 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id OAA21114; Tue, 22 Jul 1997 14:41:28 -0700 Date: Tue, 22 Jul 1997 14:41:28 -0700 From: Sean Eric Fagan Message-Id: <199707222141.OAA21114@kithrup.com> To: imp@rover.village.org Subject: Re: gcc port Cc: alpha@FreeBSD.ORG Sender: owner-freebsd-alpha@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I was going to hack the gcc in the tree to support Alpha/ELF (or more >properly alpha-dec-freebsd3.0) configuration. However, I wasn't sure >about this, due to the as/ld situation. That would probably be my choice, also. >as/ld/ et al would be much harder because our binutils are ancient. I >wasn't sure what to do about them. Should be realitvely easy to add >this support to the latest binutils, however. I'm nearly positive >they support alpha/elf to some extent. I was just going to use the new binutils, including BFD. That also handles the problem of ECOFF -- libbfd can convert, among other things. >I think that dux->freebsd cross compiler would be good. Followed >shortly by a freebsd/i386->freebsd/alpha compiler (so my PPro can be >put to good use :-). Well, I'd do a freebsd-hosted compiler chain first, of course. Since that's what I have. Porting to be hosted on DUX should be fairly simple, since gcc already supports that system. >I have an old, slightly out of date "how to build a cross compiler" >for when I was doing Linux/MIPS that can be found off of >http://www.village.org/villagers/imp somewhere. Trust me... I know how to do cross compilers :). Four+ years at cygnus may have left me nearly broke, but that is one thing I can do *REAL* well these days :). Sean.