From owner-freebsd-current Mon Feb 11 18:16:58 2002 Delivered-To: freebsd-current@freebsd.org Received: from newman2.bestweb.net (newman2.bestweb.net [209.94.102.67]) by hub.freebsd.org (Postfix) with ESMTP id EFAD437B427 for ; Mon, 11 Feb 2002 18:16:14 -0800 (PST) Received: from okeeffe.bestweb.net (okeefe.bestweb.net [209.94.100.110]) by newman2.bestweb.net (Postfix) with ESMTP id 1113D230A0 for ; Mon, 11 Feb 2002 21:16:27 -0500 (EST) Received: by okeeffe.bestweb.net (Postfix, from userid 0) id 5FE969EF23; Mon, 11 Feb 2002 21:11:37 -0500 (EST) From: jordan.breeding@attbi.com To: freebsd-current@freebsd.org Subject: Binutils fixed in -current? Date: Wed, 06 Feb 2002 19:45:14 +0000 Message-Id: <20020212021137.5FE969EF23@okeeffe.bestweb.net> 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 read recently on this list that the problem with the -current binutils on Alphas had been fixed, did this also fix the problem on i386 which caused ports such as imlib, imlib2 and gnomelibs to behave weirdly as many of their binaries would segfault during configuring/linking/executing? I only ask because I would like to stop having to update my -current tree and then having to copy an old binutils over it so that things will work. Any information is appreciated. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message