list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Jeffrey Walton <>
To: "Torsten Bögershausen" <>
Cc: Git List <>
Subject: Re: test #3 data
Date: Sat, 9 Mar 2019 20:57:07 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20190309161003.55t4irdwd76asnuf@tb-raspi4>

On Sat, Mar 9, 2019 at 11:10 AM Torsten Bögershausen <> wrote:
> On Sat, Mar 09, 2019 at 09:36:34AM -0500, Jeffrey Walton wrote:
> >
> > I'm experiencing a failure in 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...


$ 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).


  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 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \
    --subject='Re: test #3 data' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link list mirror (unofficial, one of many)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 git git/ \
	public-inbox-index git

Example config snippet for mirrors.
Newsgroups are available over NNTP:
 note: .onion URLs require Tor:

code repositories for project(s) associated with this inbox:

AGPL code for this site: git clone