From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Current SVN is broken on x86_64
Date: Mon, 4 Aug 2008 11:16:42 +0200 [thread overview]
Message-ID: <20080804091642.GB737@thorin> (raw)
In-Reply-To: <1217826161.10989.29.camel@dv>
On Mon, Aug 04, 2008 at 01:02:41AM -0400, Pavel Roskin wrote:
>
> I confirm it. And the i386-pc platform grew new warnings:
>
> kern/main.c: In function 'grub_set_root_dev':
> kern/main.c:108: warning: implicit declaration of function 'grub_free'
> loader/i386/pc/multiboot.c: In function 'grub_multiboot_load_elf32':
> loader/i386/pc/multiboot.c:165: warning: assignment makes integer from
> pointer without a cast
> loader/i386/pc/multiboot.c:168: warning: passing argument 1 of
> 'grub_memmove' makes pointer from integer without a cast
> loader/i386/pc/multiboot.c:175: warning: initialization makes pointer
> from integer without a cast
> loader/i386/pc/multiboot.c:177: warning: format '%p' expects type 'void
> *', but argument 6 has type 'Elf32_Addr'
> loader/i386/pc/multiboot.c:177: warning: format '%p' expects type 'void
> *', but argument 7 has type 'Elf32_Word'
> loader/i386/pc/multiboot.c:205: warning: format '%p' expects type 'void
> *', but argument 5 has type 'grub_addr_t'
> loader/i386/pc/multiboot.c:205: warning: format '%p' expects type 'void
> *', but argument 6 has type 'grub_size_t'
> loader/i386/pc/multiboot.c:205: warning: format '%p' expects type 'void
> *', but argument 7 has type 'grub_uint32_t'
> loader/i386/pc/multiboot.c:128: warning: unused variable
> 'physical_entry_addr'
Sorry, my bad. I'll have a look at this.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2008-08-04 9:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 0:31 Current SVN is broken on x86_64 Felix Zielcke
2008-08-04 5:02 ` Pavel Roskin
2008-08-04 9:16 ` Robert Millan [this message]
2008-08-04 9:16 ` Robert Millan
2008-08-04 12:51 ` Pavel Roskin
2008-08-04 15:11 ` Robert Millan
2008-08-04 18:27 ` Pavel Roskin
2008-08-07 12:21 ` merging i386-efi and x86_64-efi (Re: Current SVN is broken on x86_64) Robert Millan
2008-08-07 12:25 ` Robert Millan
2008-08-04 10:09 ` Current SVN is broken on x86_64 Felix Zielcke
2008-08-07 10:58 ` Current SVN is (still ?, again ?) broken Felix Zielcke
2008-08-07 12:01 ` Bean
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=20080804091642.GB737@thorin \
--to=rmh@aybabtu.com \
--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.