From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1EI0KS-0001Hp-TC for mharc-grub-devel@gnu.org; Wed, 21 Sep 2005 04:51:49 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EI0KJ-000177-Sq for grub-devel@gnu.org; Wed, 21 Sep 2005 04:51:40 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EI0Ic-0000kp-JT for grub-devel@gnu.org; Wed, 21 Sep 2005 04:50:10 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EHzwO-0007jW-Su for grub-devel@gnu.org; Wed, 21 Sep 2005 04:26:59 -0400 Received: from [146.82.138.7] (helo=master.debian.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EHzwK-0000vY-Ul for grub-devel@gnu.org; Wed, 21 Sep 2005 04:26:53 -0400 Received: from guillem by master.debian.org with local (Exim 3.35 1 (Debian)) id 1EHzwJ-0001oC-00; Wed, 21 Sep 2005 03:26:51 -0500 Date: Wed, 21 Sep 2005 11:26:59 +0300 From: Guillem Jover To: grub-devel@gnu.org Message-ID: <20050921082659.GA23629@zulo.hadrons.org> References: <87oe6nlt7j.fsf@student.han.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87oe6nlt7j.fsf@student.han.nl> User-Agent: Mutt/1.5.10i Sender: Guillem Jover Subject: Re: Building on the 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: Wed, 21 Sep 2005 08:51:45 -0000 Hi, On Tue, Sep 20, 2005 at 04:17:04PM +0200, Marco Gerards wrote: > What I didn't do is testing the result on an AMD64 box, I will do that > later (it means rebooting my desktop, which I prefer not to do that > often...). There are some warnings on the AMD64 that do not show up > on the PC. I have included all warnings in this email. Especially > the warnings about the differ in signedness confuses me, I hope > someone else knows where it comes from and how to solve it. The grub_str* functions are taking 'char *' arguments, but in some cases in the code they are given 'usigned char *' for example. 'char' is not guaranteed to be signed or usigned on a given architecture, so for strings it should not be specified. > 2005-09-20 Marco Gerards ... > * conf/i386-pc.rmk (COMMON_CFLAGS): Add `-m32'. > (COMMON_LDFLAGS): New variable. > (kernel_img_LDFLAGS): Include `COMMON_FLAGS'. > (_chain_mod_LDFLAGS, fshelp_mod_LDFLAGS, fat_mod_LDFLAGS, This should end with ')'. regards, guillem