linux-kernel - Re: cross-compiling on OS X, make menuconfig fails

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 28 Apr 2008 11:51:51 +1000
From:	tony@...eyournoodle.com (Tony Breeds)
To:	timur@...escale.com
Cc:	linux-kernel@...r.kernel.org
Subject: Re: cross-compiling on OS X, make menuconfig fails

On Sun, Apr 27, 2008 at 08:34:46PM -0500, timur@...escale.com wrote:
> I'm trying to cross-compile a PowerPC kernel from an Intel OS X system. 

<snip>
 
> 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

On most linux systems echo supports c-syle escapes with "-e".  I'm
guessing which ever echo you're getting dosesn't do that.

I think the best fix is to ensure you're getting bash as your shell.

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

But you'll likley find other palces it breaks.

Yours Tony

  linux.conf.au    http://www.marchsouth.org/
  Jan 19 - 24 2009 The Australian Linux Technical Conference!

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/