From: Jeffrey Walton <noloader@gmail.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: Git List <git@vger.kernel.org>
Subject: Re: t0028-working-tree-encoding.sh test #3 data
Date: Sat, 9 Mar 2019 20:57:07 -0500 [thread overview]
Message-ID: <CAH8yC8=01S8m8XCPoHgfX1woAEzHN7HXEn2Ncc1ceOF0SMnFaQ@mail.gmail.com> (raw)
In-Reply-To: <20190309161003.55t4irdwd76asnuf@tb-raspi4>
On Sat, Mar 9, 2019 at 11:10 AM Torsten Bögershausen <tboegi@web.de> wrote:
>
> On Sat, Mar 09, 2019 at 09:36:34AM -0500, Jeffrey Walton wrote:
> >
> > I'm experiencing a failure in t0028-working-tree-encoding.sh. The
> > first failure is test #3. The source states "source (test.utf16lebom,
> > considered UTF-16LE-BOM)" but it looks like a UTF16-LE BOM followed by
> > a UTF32-LE stream.
> >
> > Am I misunderstanding the data presentation?
>
> Thanks for the report.
>
> I think you understand it right.
>
> May be you can help us: Which OS are you using ?
Fedora 29, x86_64 fully patched.
However, I'm building Git and all of its dependencies with additional
flags for testing. The prefix directory is /var/tmp and the lib
directory is /var/tmp/lib64.
RPATHS are set for everything being built, but I don't rule out those
stupid path problems that plague Linux. In the past I have seen grep
and awk from /bin use special builds of libraries in /var/tmp/lib64. I
have not figured out how to tell programs in /bin to stop using test
libraries in /var/tmp/lib64.
> And what does
> echo "hallo" | iconv -f UTF-8 -t UTF-16 | xxd
> give ?
$ PATH=/var/tmp/bin/:$PATH echo "hallo" | iconv -f UTF-8 -t UTF-16 | xxd
00000000: fffe 6800 6100 6c00 6c00 6f00 0a00 ..h.a.l.l.o...
And:
$ PATH=/var/tmp/bin/:$PATH echo "hallo" | /usr/bin/iconv -f UTF-8 -t
UTF-16 | xxd
00000000: fffe 6800 6100 6c00 6c00 6f00 0a00 ..h.a.l.l.o...
> We may need some more debugging, may be you can send the whole log file ?
> Even if there is are a lot of ESC-sequences...
Yes, absolutely. Which file would you like?
(The only thing I can find is config.log).
Jeff
next prev parent reply other threads:[~2019-03-10 1:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 14:36 t0028-working-tree-encoding.sh test #3 data Jeffrey Walton
2019-03-09 16:10 ` Torsten Bögershausen
2019-03-10 1:57 ` Jeffrey Walton [this message]
2019-03-10 6:33 ` Torsten Bögershausen
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH8yC8=01S8m8XCPoHgfX1woAEzHN7HXEn2Ncc1ceOF0SMnFaQ@mail.gmail.com' \
--to=noloader@gmail.com \
--cc=git@vger.kernel.org \
--cc=tboegi@web.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).