From: Pavel Roskin <proski@gnu.org>
To: grub-devel@gnu.org
Subject: multiboot2.h includes stdint.h - not good
Date: Mon, 23 Mar 2009 12:56:29 -0400 [thread overview]
Message-ID: <1237827389.25031.24.camel@mj> (raw)
Hello!
The current GRUB reports this on stderr during compilation:
In file included from loader/i386/multiboot_helper.S:21:
./include/multiboot2.h:37:20: error: stdint.h: No such file or directory
In file included from loader/i386/multiboot_helper.S:21:
./include/multiboot2.h:37:20: error: stdint.h: No such file or directory
In file included from loader/i386/multiboot_helper.S:21:
./include/multiboot2.h:37:20: error: stdint.h: No such file or directory
There are two problems here. One is that stdint.h cannot be found
(apparently, the default includes are not used when compiling for the
target). Another problem is that the build succeeds despite such
errors.
I'm compiling in x86_64 environment (Fedora 10). There are no arguments
to configure, so it's compiling for i386-pc. glibc-devel-2.9-3.i386 is
installed. /usr/include/stdint.h is present (provided by
glibc-headers-2.9-3.x86_64).
By the way, I already noticed that the inclusion of stdint.h from
multiboot2.h is one of the problems preventing cross-compilation of GRUB
without the libc for the target. Perhaps GRUB should provide its
replacement for stdint.h when compiling for the target. Alternatively,
multiboot2.h should use GRUB types.
--
Regards,
Pavel Roskin
next reply other threads:[~2009-03-23 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 16:56 Pavel Roskin [this message]
2009-03-23 18:43 ` multiboot2.h includes stdint.h - not good Vesa Jääskeläinen
2009-03-24 0:38 ` Pavel Roskin
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=1237827389.25031.24.camel@mj \
--to=proski@gnu.org \
--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.