From owner-freebsd-current Fri Feb 22 4: 9:30 2002 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id B12A037B400; Fri, 22 Feb 2002 04:09:15 -0800 (PST) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.6/8.11.6) id g1MC8o229256; Fri, 22 Feb 2002 14:08:50 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200202221208.g1MC8o229256@zibbi.icomtek.csir.co.za> Subject: Re: Is any patch to situation with bad linking library on -CURRENT? In-Reply-To: <13314046938.20020222152408@telecom.ural.ru> from "Vladimir G. Drobyshevsky" at "Feb 22, 2002 03:24:08 pm" To: vlad@telecom.ural.ru (Vladimir G. Drobyshevsky) Date: Fri, 22 Feb 2002 14:08:50 +0200 (SAT) Cc: freebsd-bugs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 > > I'm sorry for possible beginning of flame, but is there exist real > solution for bad linking library problem on -CURRENT? I was noticed > about this problem about two or three weeks ago, and don't see nothing > except discussions about new binutils. It looks like the import for binutils today fixed it. At least my test case of libpng does not coredump anymore. I'll see how far a release gets. It will probably not finish because I think the dhcp stuff in the crunch files are still broken. John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message