From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Broken Build on Mac OS X
Date: Sat, 03 Dec 2005 14:00:46 +0100 [thread overview]
Message-ID: <8764q6pc75.fsf@xs4all.nl> (raw)
In-Reply-To: <E942266C-B82E-4266-B0DE-1B39801D2C91@speakeasy.net> (Andre Smith's message of "Fri, 2 Dec 2005 23:56:21 -0500")
Andre Smith <andre-smith@speakeasy.net> writes:
> gcc -Icommands -Igrub2/commands -I. -Iinclude -Igrub2/include -Wall -
> W -DGRUB_DATADIR=\"/usr/local/share/grub/powerpc-ieee1275\" -g -O2 -
> DGRUB_UTIL=1 -c -o grub_emu-commands_help.o grub2/commands/help.c
> grub2/commands/help.c: In function 'grub_cmd_help':
> grub2/commands/help.c:42: error: nested functions are not supported
> on MacOSX
> grub2/commands/help.c:65: error: nested functions are not supported
> on MacOSX
> make: *** [grub_emu-commands_help.o] Error 1
After searching a bit with google, I found this thread:
http://lists.apple.com/archives/Xcode-users/2005/Nov/msg00267.html
It seems that the apple version of gcc (?) had nested functions
disabled because of the executable stack. It seems to me that this
was done by the apple developers and not by the gcc developers.
The reason they did this was because they was to disable executable
stacks. And the way they did seems quite awkward to me. Instead of
disabling it by default they just disabled it completely. You might
have to consider building gcc yourself or using an older version.
--
Marco
next prev parent reply other threads:[~2005-12-03 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 5:00 Broken Build on Mac OS X Andre Smith
2005-12-02 14:34 ` Hollis Blanchard
2005-12-03 4:56 ` Andre Smith
2005-12-03 13:00 ` Marco Gerards [this message]
2005-12-03 17:30 ` Andre Smith
2005-12-04 2:05 ` Andrei Warkentin
2005-12-04 2:49 ` Andre Smith
2005-12-04 3:13 ` Andrei Warkentin
-- strict thread matches above, loose matches on Subject: below --
2005-12-02 17:25 andre-smith
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=8764q6pc75.fsf@xs4all.nl \
--to=mgerards@xs4all.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.