From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 22 06:20:04 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0911516A4CE for ; Mon, 22 Mar 2004 06:20:04 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id A123943D31 for ; Mon, 22 Mar 2004 06:20:01 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i2MEK0vK029051 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Mar 2004 09:20:01 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i2MEJto7018145; Mon, 22 Mar 2004 09:19:55 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16478.62987.400119.295567@grasshopper.cs.duke.edu> Date: Mon, 22 Mar 2004 09:19:55 -0500 (EST) To: Peter Wemm In-Reply-To: <200403191756.35502.peter@wemm.org> References: <16474.3985.214325.22127@grasshopper.cs.duke.edu> <200403191756.35502.peter@wemm.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: freebsd-amd64@freebsd.org Subject: Re: freebsd32 organization? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Mar 2004 14:20:04 -0000 Peter Wemm writes: <...> > I've split out the 32 bit libraries part of my current WIP. You can see > it here: http://people.freebsd.org/~peter/lib32.diff Thank you. Separating them clearly seems to be the best way. I'll let you and David decide what the prefixes should be (32 vs i386). <...> > robust with libc_r. The libpthread problem appears to be the good old > misaligned stack problem lurking somewhere. > > I'll be tackling this next. I do recommend using the 64 bit firefox > though, it is rock solid with libc_r. Excellent work in tracking down the bug. FWIW, firefox was unstable for us even after mapping libpthread -> libc_r, but I think it may have been something to do with the installed version of Xft that was discussed on -current last week. Drew