From owner-freebsd-current Wed Feb 6 12:47:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by hub.freebsd.org (Postfix) with ESMTP id F273B37B437; Wed, 6 Feb 2002 12:47:10 -0800 (PST) Received: from aldan.algebra.com (localhost [127.0.0.1]) by aldan.algebra.com (8.11.6/8.11.5) with ESMTP id g16KkPQ17117; Wed, 6 Feb 2002 15:46:27 -0500 (EST) (envelope-from mi@aldan.algebra.com) Message-Id: <200202062046.g16KkPQ17117@aldan.algebra.com> Date: Wed, 6 Feb 2002 15:46:22 -0500 (EST) From: Mikhail Teterin Subject: Re: How about gcj? (Re: Not committing WARNS settings...) To: fjoe@iclub.nsu.ru Cc: obrien@freebsd.org, current@freebsd.org In-Reply-To: <20020207023021.A51865@iclub.nsu.ru> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii 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 7 Feb, Max Khon wrote: > dynamically linked libiberty would be a nightmare. > libbfd anf libiberty do not have version numbers, are not maintained > (i.e. there is no official releases). every project includes its own > libiberty and imho an attempt to find least common denominator will > fail Well, they come to FreeBSD as part of the binutils, right? That's a good start for a version number/release :-) We don't actually build separate libbfd for linker and assembler, and separate for the compiler, do we? Any additional packages (such as those from ports) should be able to use the same libraries, IMHO, even though they may come with their own versions. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message