Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] SERIOUS bug in coreutils / cut command
Date: Wed, 22 Oct 2014 15:49:23 -0300	[thread overview]
Message-ID: <5447FC33.4060007@zacarias.com.ar> (raw)
In-Reply-To: <CAKat-EbixBqGzvLhR_utUyWKTknWF3S7=TNqfJJai1JfgOohkQ@mail.gmail.com>

On 10/22/2014 03:06 PM, Ray Cordova wrote:

> Hello,
> 
> echo "word1 word2 word3" | cut -d' ' -f1
> 
> word1
> 
> echo "word1 word2 word3" | cut -d' ' -f2
> 
> wword2 <-- ??!?!??
> 
> Yes, it really is 'wword2'.
> 
> echo "word1 word2 word3" | cut -d' ' -f3
> 
> word3
> 
> This is the September 1st, 2014 release. Coreutils 8.22. Two different
> builds, same versions, same bug.

Hi.
Works fine for me with latest git (same coreutils) using the
qemu-arm-versatile sample defconfig with the latest available external
toolchain.
How about a little more detail of architecture, toolchain and so on?
(i.e. savedefconfig defconfig)
Regards.

  reply	other threads:[~2014-10-22 18:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22 18:06 [Buildroot] SERIOUS bug in coreutils / cut command Ray Cordova
2014-10-22 18:49 ` Gustavo Zacarias [this message]
2014-10-22 20:16   ` Ray Cordova

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=5447FC33.4060007@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /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