From owner-freebsd-current Wed Jul 24 01:11:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA28395 for current-outgoing; Wed, 24 Jul 1996 01:11:39 -0700 (PDT) Received: from zed.ludd.luth.se (root@zed.ludd.luth.se [130.240.16.33]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA28355 for ; Wed, 24 Jul 1996 01:11:28 -0700 (PDT) Received: from zen.ludd.luth.se (zen.ludd.luth.se [130.240.16.34]) by zed.ludd.luth.se (8.7.5/8.7.2) with ESMTP id KAA05214; Wed, 24 Jul 1996 10:10:59 +0200 From: Joakim Henriksson Received: (murduth@localhost) by zen.ludd.luth.se (8.6.11/8.6.11) id KAA01568; Wed, 24 Jul 1996 10:10:58 +0200 Message-Id: <199607240810.KAA01568@zen.ludd.luth.se> Subject: Re: gcc 2.7.2 + binutils 2.7 on stable? To: jdp@polstra.com (John Polstra) Date: Wed, 24 Jul 1996 10:10:57 +0200 (EET DST) Cc: freebsd-current@freebsd.org In-Reply-To: <199607240429.VAA00920@austin.polstra.com> from "John Polstra" at Jul 23, 96 09:29:19 pm Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > As another option: Reportedly, it's not that hard to get just the > assembler from binutils working for FreeBSD. Our linker seems to > support weak symbols, so if you can get the binutils assembler working, > then you should be able to use it with the stock gcc-2.7.2 and the > native linker. Yeah, the assembler isn't to hard to compile. But g++ still generates code that the native ld can't handle :( But gcc seems to behave. regards/ Joakim