On 21/03/2019 01:11, Douglas R. Reno wrote: > > On 3/20/19 5:55 PM, José Carlos Carrión Plaza wrote: >>> El 19 mar 2019, a las 19:27, José Carlos Carrión Plaza <[email protected]> >>> escribió: >>> >>>> El 19 mar 2019, a las 17:14, Bruce Dubbs <[email protected]> escribió: >>>> >>>> On 3/19/19 11:05 AM, José Carlos Carrión Plaza wrote: >>>>> Enviado desde mi iPhone >>>>>>> El 19 mar 2019, a las 14:46, Pierre Labastie <[email protected]> >>>>>>> escribió: >>>>>>> >>>>>>> On 19/03/2019 13:43, José Carlos Carrión Plaza wrote: >>>>>>> Hello co-listers: >>>>>>> >>>>>>> I’ve installed LFS 8.4. I’ve built several BLFS packages without >>>>>>> problem and X-Window is running (with motif-2.3.8). At the booting of >>>>>>> MariadB I’ve detected the following problem: >>>>>>> >>>>>>> -bash-5.0# echo foobar | LANG=POSIX cut -c4 >>>>>>> b >>>>>>> -bash-5.0# echo foobar | LANG=en_US.iso8859-1 cut -c4 >>>>>>> b >>>>>>> -bash-5.0# echo foobar | LAN=en_US.utf8 cut -c4 >>>>>> Seems "G" is missing at the end of "LAN". >>>>>> >>>>>>> -bash-5.0# >>>>>>> >>>>>>> I’m almost sure I’ve properly applied the coreutils-8.30-i18n-1.patch >>>>>>> at LFS chapter 6. Just in case, I’ve rebuilt coreutils-8.30 applying >>>>>>> patch with a clean environment: >>>>>>> >>>>>>> -bash-5.0$ env -i TERM="$TERM" HOME=“$HOME" >>>>>>> PATH="/bin:/sbin:/usr/bin:/usr/sbin" LC_ALL=POSIX /bin/bash >>>>>>> bash-5.0$ >>>>>>> >>>>>>> I’ve built coreutils (with patch, indeed) as LFS book reads without >>>>>>> problem and all tests passed, but test-getlogin as expected. >>>>>>> The problem with cut command remains. >>>>>>> >>>>>>> What (and where) I’ve made the mistake? Is it safe to continue? >>>>> Of course. It’s a typo. >>>>> -bash-5.0# echo foobar | LANG=en_US.utf8 cut -c4 >>>>> gives no output >>>> It does for me: >>>> >>>> $ echo foobar | LANG=en_US.utf8 cut -c4 >>>> b >>>> >>>> — Bruce >>>> >>> Maybe the architecture? I’m on i686… >>> >> Answering myself... >> >> On x86_64: >> >> $ echo foobar | LANG=en_US.utf8 cut -c4 >> b >> >> With the permission of masters, I’m going to regard on coreutils patch >> looking for an architecture bug. >> >> Regards. >> >> J. C. > > > Chiming in here, > > > I just ran a test on my i686 box while waiting for a build to complete. > > > renodr [ /sources ]$ echo foobar | LANG=en_US.UTF-8 cut -c4 > > > renodr [ /sources ]$ > > I'm not getting any output either. > > It's running 20190101-systemd >
On a i686 VM (lfs svn around the middle of January): ---------- pierre [ ~ ]$ locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= pierre [ ~ ]$ echo foobar | cut -c 4 pierre [ ~ ]$ echo foobar | cut -c 4- bar -------- That is "4-" works as expected. Could help to narrow the search. Also we should test if fedora (or Suse) have the same bug. If not, they may have fixed their patch. Pierre -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
