Re: tar: Can't translate pathname 'xxx' to UTF-8

[Taylor R Campbell <riastradh%NetBSD.org@localhost>]

> Date: Fri, 25 Sep 2026 23:02:30 +0100
> From: Jonathan Perkin <jperkin%pkgsrc.org@localhost>
> 
> * On 2026-09-25 at 22:46 BST, Taylor R Campbell wrote:
> 
> >> Date: Fri, 25 Sep 2026 22:38:28 +0100
> >> From: Jonathan Perkin <jperkin%pkgsrc.org@localhost>
> >>
> >> If building archivers/bsdtar with iconv support helps avoid some of
> >> these issues then we should just do that.  It's not in the core
> >> bootstrap path - it's only pulled in as a post-bootstrap dependency if a
> >> package declares EXTRACT_USING=bsdtar and the host system does not
> >> provide one.
> >
> >bsdtar may not be, but libarchive is as a mandatory dependency of
> >pkg_install, and we only have one way to build libarchive at the
> >moment which both bootstrap and pkg_install and archivers/bsdtar all
> >share, as far as I'm aware.
> 
> bootstrap and pkg_install build their own internal copy of libarchive 
> and statically link it, so the main libarchive package would still be 
> free to be fully-featured.
> 
> Unless there are extra patches I have that I'm forgetting about (I know 
> my pkgin-is-statically-linked-too patch is custom).

No objection here to the goal, I just don't know all the constraints
that are involved, so I'm simply echoing what's written in the bsdtar
and libarchive Makefiles:

// bsdtar/Makefile
# Explicitly do not depend on libtool as this can be used
# as bootstrap dependency.
#USE_LIBTOOL=		yes
CONFIGURE_ARGS+=	--enable-bsdtar=static
...
CONFIGURE_ARGS+=	--without-iconv

// libarchive/Makefile
BOOTSTRAP_PKG=		yes
...
CONFIGURE_ARGS+=	--without-iconv