From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 17 02:22:00 2005 Return-Path: X-Original-To: amd64@freebsd.org 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 0128D16A420 for ; Wed, 17 Aug 2005 02:22:00 +0000 (GMT) (envelope-from mi+kde@aldan.algebra.com) Received: from mail27.sea5.speakeasy.net (mail27.sea5.speakeasy.net [69.17.117.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2994343D48 for ; Wed, 17 Aug 2005 02:21:59 +0000 (GMT) (envelope-from mi+kde@aldan.algebra.com) Received: (qmail 1600 invoked from network); 17 Aug 2005 02:21:58 -0000 Received: from aldan.algebra.com (HELO blue.virtual-estates.net) ([216.254.65.224]) (envelope-sender ) by mail27.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 17 Aug 2005 02:21:58 -0000 Received: from blue.virtual-estates.net (blue [127.0.0.1]) by blue.virtual-estates.net (8.13.3/8.13.3) with ESMTP id j7H2Lvmq030475; Tue, 16 Aug 2005 22:21:57 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by blue.virtual-estates.net (8.13.3/8.13.3/Submit) id j7H2LvAb030474; Tue, 16 Aug 2005 22:21:57 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) X-Authentication-Warning: blue.virtual-estates.net: mi set sender to mi+kde@aldan.algebra.com using -f From: Mikhail Teterin To: voisine@gmail.com Date: Tue, 16 Aug 2005 22:21:56 -0400 User-Agent: KMail/1.8.1 X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7whJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Cc: amd64@freebsd.org, gnome@freebsd.org Subject: using linux-firefox on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2005 02:22:00 -0000 Hi! I found, that the only way to use the linux-firefox (a 32-bit Linux binary) on amd64 is by removing the ~/.fonts.cache-1 prior to starting it -- the process gets SIGILL on startup otherwise. Is that because the file is architecture specific, or because the versions of whatever library maintains it (freetype?) differ too much between FreeBSD's native and what's installed by linux compatability ports (linux_base-8 in my case)? -mi