Russell Warren wrote:
> > In fact, libunistring relies on the iconv API (in libc or libiconv), not on
> > the 'iconv' program.
> >
>
> That is what I thought as well, so I had deleted the iconv executable in my
> build script. This caused the 22 failures. The only change made between 22
> failure
On Sun, Jul 2, 2023, 7:55 AM Bruno Haible wrote:
> In fact, libunistring relies on the iconv API (in libc or libiconv), not on
> the 'iconv' program.
>
That is what I thought as well, so I had deleted the iconv executable in my
build script. This caused the 22 failures. The only change made bet
[CCing bug-libunistring, which is the better forum for topics like this.]
> > After a build of libunistring 1.1 I am running `make check` and am getting
> > 22 failures:
> >
> >
> >
> > Testsuite summary for
> >
> > =
Never mind. The iconv executable was not available. Restoring that brings
it back to zero errors.
Apologies for the noise.
On Sat, Jul 1, 2023 at 3:37 PM Russell Warren wrote:
> Hello,
>
> After a build of libunistring 1.1 I am running `make check` and am getting
> 22 failures:
>
>
>
Hello,
After a build of libunistring 1.1 I am running `make check` and am getting
22 failures:
Testsuite summary for
# TOTAL: 582
# PASS: 522
