From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1CsPap-0001Kh-H0 for mharc-grub-devel@gnu.org; Sat, 22 Jan 2005 13:02:40 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CsPYt-0000b9-VS for grub-devel@gnu.org; Sat, 22 Jan 2005 13:00:40 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CsPYY-0000Uq-0E for grub-devel@gnu.org; Sat, 22 Jan 2005 13:00:20 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CsPYV-0000PJ-Me for grub-devel@gnu.org; Sat, 22 Jan 2005 13:00:17 -0500 Received: from [212.43.237.68] (helo=kotoba.storever.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CsP9S-0002Kq-K7 for grub-devel@gnu.org; Sat, 22 Jan 2005 12:34:22 -0500 Received: from ASSP-nospam (localhost [127.0.0.1]) by kotoba.storever.com (Postfix) with ESMTP id 0D9CEF8E0AC2 for ; Sat, 22 Jan 2005 18:34:18 +0100 (CET) Received: from 127.0.0.1 ([127.0.0.1] helo=localhost) by ASSP-nospam ; 22 Jan 05 17:34:17 -0000 From: "Yoshinori K. Okuji" Organization: enbug.org To: The development of GRUB 2 Date: Sat, 22 Jan 2005 18:34:40 +0100 User-Agent: KMail/1.7.1 References: <20050122143259.GA19529@openbios.org> <87oefh5wf2.fsf@marco.marco-g.com> In-Reply-To: <87oefh5wf2.fsf@marco.marco-g.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501221834.40912.okuji@enbug.org> Subject: Re: building grub on AMD64 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: Sat, 22 Jan 2005 18:02:38 -0000 On Saturday 22 January 2005 16:13, Marco Gerards wrote: > Stefan Reinauer writes: > > with the attached patch grub2 can be built on AMD64 systems. > > It is not completely clean I would say, but it solves the problem > > with minimum impact. > > Please dont tare my head off ;-) > > > > It is necessary to call autoconf before the code can be used. > > Cool. It looks fine to me, but I have little knowledge of the build > process, unfortunately. I hope someone with more clue about autoconf > have a look. It looks not fine to me. Why is host_cpu set to target_cpu? They must be distinguished correctly. Okuji