From: "Yves BLUSSEAU" <cl7m42e02@sneakemail.com>
To: grub-devel@gnu.org
Subject: Mac OSX Ports
Date: Tue, 30 Jun 2009 11:35:39 +0200 [thread overview]
Message-ID: <28509-35725@sneakemail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
Hi,
i'm currently trying to ports grub2 to Mac OSX (leopard).
I can compil and build the code with XCode.
I have add the necessary functions and calls to support OSX (like
getting block counts of a block device with ioctl calls).
The only problem is the hook nested functions. XCode disable nested
functions by defaut.
So i enabled it with the gcc option -fnested-functions: all compil and
build right but i have exceptions at runtime.
If i put nested functions outside (putting also inner variables
outside) i fix the problem and all work well.
So do you know if it exists a gcc option or a linker option to fix this
nested functions problem ?
Also where or at who i can sent my OSX patchs for incorporating into
the main trunk ?
Thanks in advance,
Yves Blusseau
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3313 bytes --]
next reply other threads:[~2009-06-30 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 9:35 Yves BLUSSEAU [this message]
2009-06-30 10:32 ` Mac OSX Ports Vladimir '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=28509-35725@sneakemail.com \
--to=cl7m42e02@sneakemail.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.