From owner-freebsd-current Tue May 14 21: 7:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 4605C37B401; Tue, 14 May 2002 21:07:06 -0700 (PDT) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.3/8.12.2) with ESMTP id g4F475fg036864; Tue, 14 May 2002 21:07:05 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.3/8.12.3/Submit) id g4F475eQ036863; Tue, 14 May 2002 21:07:05 -0700 (PDT) Date: Tue, 14 May 2002 21:07:05 -0700 From: "David O'Brien" To: Bruce Evans Cc: Ruslan Ermilov , current@FreeBSD.ORG Subject: Re: [PATCH] cross-arch bootstrapping is broken by GCC 3.1 Message-ID: <20020514210705.A36814@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG Mail-Followup-To: David O'Brien , Bruce Evans , Ruslan Ermilov , current@FreeBSD.ORG References: <20020514120758.D31896@dragon.nuxi.com> <20020515130406.S6466-100000@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020515130406.S6466-100000@gamplex.bde.org>; from bde@zeta.org.au on Wed, May 15, 2002 at 01:16:23PM +1000 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, May 15, 2002 at 01:16:23PM +1000, Bruce Evans wrote: > > > 4.x i386 and old 5.0 i386 can no longer produce current 5.0 alpha > > > worlds due to the lack of atoll(3) in libc. This patch fixes it: > > > > Considering how simple src/lib/libc/stdlib/atoll.c is; lets ask RE for a > > MFC. > > That wouldn't actually fix the problem, since it would only help for > bootstrapping 5.0 from very recent versions of 4.x. Personally I do not mind requiring latest 4-STABLE to build -CURRENT (either for cross or simple `world'). I think that is all we can officially support. I know RU wants to be able to upgrade from say 4.1 to 5-CURRENT. I think that is a nice thing; but if it is going to be a requirement it should become an officially stated one. The only fix is to import all of libiberty and create a config.h that implies Version 7. > The problem is the usual one with committing files generated by > autoconfig. It would be the same problem without autoconf, the code could have been written only the the 5-CURRENT API. > This gives a configuration that might only be valid for the host > machine that ran autoconfig. Cross-compiling of even portable > cross-compile-aware sources like gcc is broken by this. I personally believe we should build GCC in the normal manner, but this is no longer my decision to make. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message