From: Timur Tabi <timur@tabi.org>
To: linux-kernel@vger.kernel.org
Subject: cross-compiling on OS X, make menuconfig fails
Date: Sun, 27 Apr 2008 20:34:35 -0500 [thread overview]
Message-ID: <481529AB.7050304@tabi.org> (raw)
I'm trying to cross-compile a PowerPC kernel from an Intel OS X system.
I've almost got it working, except "make menuconfig" dies. It says
I'm missing ncurses:
*** Unable to find the ncurses libraries or the
*** required header files.
*** 'make menuconfig' requires the ncurses libraries.
However, I do not think that ncurses is the real problem, since I do
have ncurses installed. I think the real problem is that the
check-lxdialog.sh is trying to execute this code:
echo -e ' #include CURSES_LOC \n main() {}' | gcc
'-DCURSES_LOC=<ncurses.h>' -DLOCALE -DKBUILD_NO_NLS -lncurses -xc - -o
.lxdialog.tmp
And the compiler is failing with this output:
<stdin>:1: error: syntax error before ‘-’ token
<stdin>:1: error: stray ‘#’ in program
So something strange is going on. Has anyone been able to cross-compile
from an Intel Mac running OS X?
next reply other threads:[~2008-04-28 1:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 1:34 Timur Tabi [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-28 1:34 cross-compiling on OS X, make menuconfig fails timur
2008-04-28 1:51 ` Tony Breeds
2008-04-29 15:07 ` Timur Tabi
2008-04-29 16:45 ` Sam Ravnborg
2008-04-29 17:20 ` Al Viro
2008-04-29 18:06 ` Sam Ravnborg
2008-04-30 13:54 ` Timur Tabi
2008-04-30 14:18 ` Sam Ravnborg
2008-05-03 6:55 ` SL Baur
2008-05-03 8:01 ` Sam Ravnborg
2008-05-03 8:40 ` Roland Kuhn
2008-05-03 9:34 ` SL Baur
2008-05-12 13:22 ` Arnd Hannemann
2008-04-28 18:46 ` Roland Kuhn
2008-04-29 14:51 ` Timur Tabi
2008-04-29 16:45 ` Sam Ravnborg
2008-04-29 16:48 ` Al Viro
2008-04-29 22:46 ` Bernd Petrovitsch
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=481529AB.7050304@tabi.org \
--to=timur@tabi.org \
--cc=linux-kernel@vger.kernel.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.