linux-kernel - Re: [PATCH] scripts/Kbuild.include: Fix portability problem of "echo -e"

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]

Message-ID: <4F4D6532.4010906@biessmann.de>
Date:	Wed, 29 Feb 2012 00:37:22 +0100
From:	Andreas Bießmann <andreas@...ssmann.de>
To:	Bernhard Walle <bernhard@...lle.de>
CC:	mmarek@...e.cz, lacombar@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] scripts/Kbuild.include: Fix portability problem of "echo
 -e"


On 26.02.12 18:35, Bernhard Walle wrote:
> "echo -e" is a GNU extension. When cross-compiling the kernel on a
> BSD-like operating system (Mac OS X in my case), this doesn't work.
> 
> One could install a GNU version of echo, put that in the $PATH before
> the system echo and use "/usr/bin/env echo", but the solution with
> printf is simpler.
> 
> Since it is no disadvantage on Linux, I hope that gets accepted even if
> cross-compiling the Linux kernel on another Unix operating system is
> quite a rare use case.
> 
> Signed-off-by: Bernhard Walle <bernhard@...lle.de>

Tested-by: Andreas Bießmann <andreas@...ssmann.de>

Without that patch cross-compiling kernel for omap2 devices on BSD-style
hosts is broken.
For x86 targets the impact is not that hard but CFI is omitted even
though it is supported by assembler (in one case this led to a devious
error message pointing to a assembler bug in my cross toolchain).

So please consider applying this patch.
--
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/