From: Marco Gerards <metgerards@student.han.nl>
To: Johan Rydberg <jrydberg@night.trouble.net>
Cc: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: multiboot
Date: Wed, 08 Dec 2004 19:10:33 +0000 [thread overview]
Message-ID: <874qiw7gie.fsf@marco.marco-g.com> (raw)
In-Reply-To: <873bygpzzi.fsf@night.trouble.net> (Johan Rydberg's message of "Wed, 08 Dec 2004 16:32:33 +0100")
Johan Rydberg <jrydberg@night.trouble.net> writes:
> Marco Gerards <metgerards@student.han.nl> writes:
>
>> Johan Rydberg <jrydberg@night.trouble.net> writes:
>>
>>> The initial problem was that AC_CHECK_SIZEOF doesn't work if you're
>>> cross-compiling. I fixed this by using AC_COMPILE_CHECK_SIZEOF [1]
>>> instead.
>>
>> This sounds right to me, but I do not see this in the patch...
>
> Of course not. I didn't include it :) I'm sure you can download the
> m4 macro, install it in acinclude.m4 and change AC_CHECK_SIZEOF to
> AC_COMPILE_CHECK_SIZEOF. If you're as lazy as I am, I can include it
> in a later patch.
As you know, I am lazy... ;)
>>> But the major problem is that parts of GRUB2 requires a C library to
>>> be installed, at least headers such as alloca.h and stdint.h. Is this
>>> really a valid demand?
>>
>> Is this required for grubof? IIRC those headers are not a part of the
>> C library, but a part of gcc or libgcc or so. Am I right about that?
>
> My GCC installation (3.2.2 configured for powerpc-elf) installed the
> following headers:
[...]
> A little more research shows that both stdint.h and alloca.h is part
> of glibc:
[...]
> So either we stop using then, or write our own versions.
Ok, agreed.
>> Instead of alloca we can also use something like:
>> [...]
>> In most cases that will remove the dependency on alloca. IMHO it is
>> better not to use alloca.
>
> It is also possible to use __builtin_alloca if alloca.h is missing,
> provided that there's a requirement for GCC.
There is a gcc requirement already, that is not a problem.
Thanks,
Marco
next prev parent reply other threads:[~2004-12-08 21:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 11:09 multiboot Johan Rydberg
2004-12-07 14:51 ` multiboot Marco Gerards
2004-12-08 10:44 ` multiboot Johan Rydberg
2004-12-08 11:59 ` multiboot Marco Gerards
2004-12-08 12:27 ` multiboot Johan Rydberg
2004-12-08 12:23 ` multiboot Marco Gerards
2004-12-08 13:24 ` multiboot Johan Rydberg
2004-12-08 13:34 ` multiboot Johan Rydberg
2004-12-08 14:57 ` multiboot Marco Gerards
2004-12-08 15:32 ` multiboot Johan Rydberg
2004-12-08 19:10 ` Marco Gerards [this message]
2004-12-09 2:16 ` multiboot Yoshinori K. Okuji
2004-12-09 11:42 ` multiboot Johan Rydberg
2004-12-09 13:51 ` multiboot Marco Gerards
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=874qiw7gie.fsf@marco.marco-g.com \
--to=metgerards@student.han.nl \
--cc=grub-devel@gnu.org \
--cc=jrydberg@night.trouble.net \
/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.