From: Timur Tabi <timur@freescale.com>
To: Tony Breeds <tony@bakeyournoodle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cross-compiling on OS X, make menuconfig fails
Date: Tue, 29 Apr 2008 10:07:43 -0500 [thread overview]
Message-ID: <481739BF.8010305@freescale.com> (raw)
In-Reply-To: <20080428015151.GW20457@bakeyournoodle.com>
Tony Breeds wrote:
> On most linux systems echo supports c-syle escapes with "-e". I'm
> guessing which ever echo you're getting dosesn't do that.
Yes, that is my problem.
> I think the best fix is to ensure you're getting bash as your shell.
The script starts off with this line:
#!/bin/sh
Doesn't that mean that it should be interpreted by sh and not bash?
> A nasty hack would be to make check-lxdialog.sh do something like:
> (echo ' #include CURSES_LOC';echo 'main() {}') | gcc '-DCURSES_LOC=<ncurses.h>' -DLOCALE -DKBUILD_NO_NLS -lncurses -xc - -o .lxdialog.tmp
This works. Do you think if I posted a patch that makes this change, it will be
accepted?
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-04-29 15:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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 20:27 ` Why use /bin/sh in kernel build system? Mark Rustad
2008-04-29 21:41 ` Alexey Dobriyan
2008-04-29 22:24 ` Willy Tarreau
2008-04-29 22:40 ` Timur Tabi
2008-04-30 9:42 ` SL Baur
2008-04-30 11:48 ` Jan Engelhardt
2008-04-29 22:46 ` cross-compiling on OS X, make menuconfig fails Bernd Petrovitsch
-- strict thread matches above, loose matches on Subject: below --
2008-04-28 1:34 Timur Tabi
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=481739BF.8010305@freescale.com \
--to=timur@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@bakeyournoodle.com \
/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.