From owner-freebsd-current@FreeBSD.ORG Sun Feb 11 15:21:22 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 72E2C16A400 for ; Sun, 11 Feb 2007 15:21:22 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from pobox.codelabs.ru (pobox.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id 2E28B13C471 for ; Sun, 11 Feb 2007 15:21:22 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from codelabs.ru (pobox.codelabs.ru [144.206.177.45]) by pobox.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1HGGKg-000Nmw-C6; Sun, 11 Feb 2007 18:09:38 +0300 Date: Sun, 11 Feb 2007 18:09:33 +0300 From: Eygene Ryabinkin To: Robert Noland Message-ID: <20070211150933.GK73008@codelabs.ru> References: <45CA7D23.8050501@criticalmagic.com> <1170980071.18185.12.camel@rnoland-ibm.acs.internap.com> <20070211150703.GJ73008@codelabs.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20070211150703.GJ73008@codelabs.ru> Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-2.1 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_50 Cc: Michiel Boland , freebsd-current@freebsd.org, Richard Coleman Subject: Re: latest xorg port compiles but does not run on sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Feb 2007 15:21:22 -0000 > I do not know what's happened, but the attached file should go to > the x11-servers/xorg-server/files/ directory and overwrite the original > patch-FreeBSD.cf. Basically, it adds the --export-dynamic flag for > the linker to make global symbols in Xorg to be visible to the > dlopen()/dlsym(), since this is the immediate reason for failures. Forgot to say: it is not sparc64-specific: I have this error on i386 too. Seems like it is not the arch-specific problem. -- Eygene