public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas@biessmann.de>
To: Bernhard Walle <bernhard@bwalle.de>
Cc: mmarek@suse.cz, lacombar@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts/Kbuild.include: Fix portability problem of "echo -e"
Date: Wed, 29 Feb 2012 00:37:22 +0100	[thread overview]
Message-ID: <4F4D6532.4010906@biessmann.de> (raw)
In-Reply-To: <1330277718-2667-1-git-send-email-bernhard@bwalle.de>


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@bwalle.de>

Tested-by: Andreas Bießmann <andreas@biessmann.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.

      parent reply	other threads:[~2012-02-28 23:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-26 17:35 [PATCH] scripts/Kbuild.include: Fix portability problem of "echo -e" Bernhard Walle
2012-02-26 17:48 ` Sam Ravnborg
2012-02-26 17:51   ` Bernhard Walle
2012-02-26 21:05     ` Sam Ravnborg
2012-03-19 17:44       ` Bernhard Walle
2012-03-24 22:33         ` Michal Marek
2012-02-28 23:37 ` Andreas Bießmann [this message]

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=4F4D6532.4010906@biessmann.de \
    --to=andreas@biessmann.de \
    --cc=bernhard@bwalle.de \
    --cc=lacombar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox