From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.33) id 1Cjk0S-0000lK-Ie for mharc-grub-devel@gnu.org; Wed, 29 Dec 2004 15:01:16 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1Cjk0G-0000gQ-0U for grub-devel@gnu.org; Wed, 29 Dec 2004 15:01:04 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1Cjk0B-0000eF-KN for grub-devel@gnu.org; Wed, 29 Dec 2004 15:01:01 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Cjk0B-0000dz-HH for grub-devel@gnu.org; Wed, 29 Dec 2004 15:00:59 -0500 Received: from [145.74.66.11] (helo=mail-cn.han.nl) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Cjjmt-0002OZ-Hf for grub-devel@gnu.org; Wed, 29 Dec 2004 14:47:15 -0500 Received: from vscan-ca.han.nl (mars.han.nl [145.74.129.116]) by mail-cn.han.nl (Postfix) with ESMTP id 16CA99ED0 for ; Wed, 29 Dec 2004 20:47:15 +0100 (CET) Received: from mail-cn.han.nl ([145.74.66.51]) by vscan-ca.han.nl (mars.han.nl [145.74.129.116]) (amavisd-new, port 10024) with LMTP id 11543-07-61 for ; Wed, 29 Dec 2004 20:47:12 +0100 (CET) Received: from mail1.han.nl (mail1.han.nl [145.74.103.11]) by mail-cn.han.nl (Postfix) with ESMTP id D2D249ECC for ; Wed, 29 Dec 2004 20:47:11 +0100 (CET) Received: from marco.marco-g.com (mgerards.xs4all.nl [82.92.27.129]) by mail1.han.nl (Postfix) with ESMTP id 6CEC7C056 for ; Wed, 29 Dec 2004 20:47:11 +0100 (CET) Mail-Copies-To: metgerards@student.han.nl To: The development of GRUB 2 References: <200411231701.07309.T.E.Baldwin99@members.leeds.ac.uk> <200411271821.34605.T.E.Baldwin99@members.leeds.ac.uk> <87eki7ledn.fsf@marco.marco-g.com> <200412041030.53638.T.E.Baldwin99@members.leeds.ac.uk> From: Marco Gerards Date: Wed, 29 Dec 2004 19:46:34 +0000 In-Reply-To: <200412041030.53638.T.E.Baldwin99@members.leeds.ac.uk> (Timothy Baldwin's message of "Sat, 4 Dec 2004 10:30:21 +0000") Message-ID: <87sm5oj3ad.fsf@marco.marco-g.com> User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new (2.2.0) at vscan-ca.han.nl Subject: Re: RISC OS port 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, 29 Dec 2004 20:01:04 -0000 Timothy Baldwin writes: Whoops, I just noticed I forgot to answer this email... :/ >> > Define BUILD to "build/" when cross compiling or to "" >> > when not cross-compiling and prefix use of the utilites >> > in makefiles with $(BUILD). >> > >> > Shall I do that? >> >> This does not look like a clean solution to me. > >> Normally this is not >> required to do it like this, right? > > The gcc package also uses multiple runs of configure. > > You're right, genmoddep does not require the services of configure, > but then why was support for checking the build system compiler > added to configure.ac? > > I suggest removing that support, and only use BUILD_CC for compiling > genmoddep. Support for building cross versions of the tools could be > retained by supporting configure's --target option. So you mean you can choose if grub-mkimage is compiled for the host or target system? I think that would be useful. Considering two scenarios: 1) Building the PPC version of GRUB using a PC. In the case grub-mkimage (the one form the ieee1275/ppc directory) works on the PC, I can make an ELF including some modules. This is really useful when developing. 2) When cross-compiling a Debian package, everything has to be build for the host, with some specific tools used in the buildprocess as an exception. So if configure somehow supports this in a sane way, it would seem nice to have. As most people here know, I am quite clueless about the autotools... :/ >> Why do you need perl? > > A perl program is used to convert the list of machine names > and numbers from Linux. I have my doubts about adding a dependency for perl to GRUB, although it is required for automake too. So when is it required, when the developers change something or when a user wants to compile it? >> Can't you use GRUB_ERR_BAD_FS >> or GRUB_FS_BAD_FILE_TYPE instead? > > The error is probably not one of those, and could almost anything. Sorry, I do not understand what you mean. > > >> > +void *EXPORT_FUNC(memcpy) (void *dest, const void *src, grub_size_t n); >> > +void *EXPORT_FUNC(memset) (void *s, int c, grub_size_t n); >> >> Why do you want to do this? Can't you just use grub_memcpy and >> grub_memset instead? > > They are called implictally by gcc. Right. I had stuff like this in the PPC port as well. Perhaps you can make a libgcc.h, like I did for the PPC port? >> > -#define FUNCTION(x) .globl EXT_C(x) ; .type EXT_C(x), @function ; EXT_C(x): >> > -#define VARIABLE(x) .globl EXT_C(x) ; .type EXT_C(x), @object ; EXT_C(x): >> > +#define FUNCTION(x) .globl EXT_C(x) ; .type EXT_C(x), "function" ; EXT_C(x): >> > +#define VARIABLE(x) .globl EXT_C(x) ; .type EXT_C(x), "object" ; EXT_C(x): >> >> Can you please explain this change? > > "@" marks the start of a comment in ARM GNU as syntax, producing a syntax > error. I expect double quotes to work for all architures. Tested on x86 and PowerPC. Ok. Thanks, Marco