All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: RISC OS port
Date: Fri, 03 Dec 2004 13:07:00 +0000	[thread overview]
Message-ID: <87eki7ledn.fsf@marco.marco-g.com> (raw)
In-Reply-To: <200411271821.34605.T.E.Baldwin99@members.leeds.ac.uk> (Timothy Baldwin's message of "Sat, 27 Nov 2004 18:21:25 +0000")

Timothy Baldwin <tim.lists@majoroak.f2s.com> writes:

> On Saturday 27 Nov 2004 01:36, I wrote:
>
>> 1. Portability fixes and configure.ac changes.
>
> Here they are. However cross-compiling is broken in that
> the utilities are only built for the build system, without
> this patch they are only built for the host system. Either
> way, the result is not a complete installation.

Ok.  I really hope someone else can have a look at this because I
don't know much about autoconf/automake, etc.  However, I am trying to
comment on your code wherever I can.

> I propose to solve this problem by running configure twice
> when cross-compiling, once for the host, once for the build
> system. This could be done by adding these make rules:
>
> build/%: build/Makefile
>  cd build && $(MAKE) $*
>  touch $@
>
> build/Makefile: $(srcdir)/configure
>  cd build && $(srcdir)/configure --host=$(build) --target=$(host)
>
> 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?

Can you please make a changelog entry for this patch?

> +if test "x$host_cpu" = xarm; then
> +  AC_PATH_PROG(PERL, perl)
> +fi
> +

Why do you need perl?

> +    GRUB_ERR_FILE_CLOSE_ERROR,
> +    GRUB_ERR_FILE_OPEN_ERROR,
> +    GRUB_ERR_DIR_READ_ERROR

When are these errors triggered, btw?  Can't you use GRUB_ERR_BAD_FS
or GRUB_FS_BAD_FILE_TYPE instead?


> diff -purN -x '*.mk' -x '*~' -x autom4te.cache -x configure -x '.#*' -x CVS grub2-submitted/include/grub/misc.h grub2-arm/include/grub/misc.h
> --- grub2-submitted/include/grub/misc.h 2004-11-19 00:55:52.000000000 +0000
> +++ grub2-arm/include/grub/misc.h 2004-11-26 21:46:02.000000000 +0000

...

> +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?

> -#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?
>  }
> +
>  void *memmove (void *dest, const void *src, grub_size_t n)
>    __attribute__ ((alias ("grub_memmove")));
> +

Please watch out with adding white lines.



Does GRUB 2 still work on the PC after this patch is committed?

Thanks,
Marco




  reply	other threads:[~2004-12-03 13:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23 17:00 RISC OS port Timothy Baldwin
2004-11-23 18:03 ` Marco Gerards
2004-11-26  0:47   ` Timothy Baldwin
2004-11-26 10:18     ` Marco Gerards
2004-11-26 12:57       ` Yoshinori K. Okuji
2004-11-27  1:36       ` Timothy Baldwin
2004-11-27 18:21         ` Timothy Baldwin
2004-12-03 13:07           ` Marco Gerards [this message]
2004-12-04 10:30             ` Timothy Baldwin
2004-12-29 19:46               ` Marco Gerards
2004-12-03 12:53         ` Marco Gerards
2004-12-03 13:51           ` Johan Rydberg
2004-12-04 10:27           ` Timothy Baldwin
2004-12-04 13:14             ` Marco Gerards
  -- strict thread matches above, loose matches on Subject: below --
2013-05-03 11:49 Vladimir 'φ-coder/phcoder' Serbinenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87eki7ledn.fsf@marco.marco-g.com \
    --to=metgerards@student.han.nl \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.