From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1JE8uO-0005JU-FX for mharc-grub-devel@gnu.org; Sun, 13 Jan 2008 14:54:16 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JE8uK-0005FN-Oe for grub-devel@gnu.org; Sun, 13 Jan 2008 14:54:13 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JE8uI-0005EA-DV for grub-devel@gnu.org; Sun, 13 Jan 2008 14:54:10 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JE8uH-0005E1-Vq for grub-devel@gnu.org; Sun, 13 Jan 2008 14:54:10 -0500 Received: from ns39764.ovh.net ([91.121.25.85] helo=nexedi.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JE8uH-0007uT-O9 for grub-devel@gnu.org; Sun, 13 Jan 2008 14:54:09 -0500 Received: from [10.8.0.46] (unknown [10.8.0.46]) by nexedi.com (Postfix) with ESMTP id 845603EB24; Sun, 13 Jan 2008 20:59:15 +0100 (CET) From: "Yoshinori K. Okuji" Organization: enbug.org To: grub-devel@gnu.org Date: Sun, 13 Jan 2008 20:53:49 +0100 User-Agent: KMail/1.9.4 References: <20071222194111.GA8254@durotan.0x539.de> <20071226092116.GA26341@thorin> <20080113121903.GA25723@thorin> In-Reply-To: <20080113121903.GA25723@thorin> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801132053.50100.okuji@enbug.org> X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) Cc: Philipp Kern , 457491@bugs.debian.org, Robert Millan Subject: Re: Fwd: grub2: FTBFS on powerpc (__floatundisf in ls is not defined) X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2008 19:54:15 -0000 On Sunday 13 January 2008 13:19, Robert Millan wrote: > This is becoming a nightmare. I think it's better if we just exclude > symbols starting with __ from our checks. They aren't really meant for us > to mess with. My original suggestion was that we could extract (required) symbols from libgcc, and export them from the kernel. I think this can be automated. Okuji