-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 11/25/2014 13:22, Dr. Peter Voigt wrote:
> I am currently unable to upgrade tex-xetex and tex-luatex on 
> 10.1-RELEASE (amd64).
> 
> 
> # portmaster --no-confirm --no-term-title -D -G tex-xetex ... 
> mktexlsr: Done. /bin/cat
> /usr/ports/print/tex-xetex/work/fmtutil.cnf |  while read format
> dum; do  /usr/bin/env 
> PATH=/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/ports/print/tex-xetex/work/stage/usr/local/bin:/usr/local/bin
>
> 
TEXMFDIST=/usr/ports/print/tex-xetex/work/stage/usr/local/share/texmf-dist:/usr/local/share/texmf-dist
 /usr/local/bin/fmtutil-sys
> --byfmt $format --fmtdir
> /usr/ports/print/tex-xetex/work/stage/usr/local/share/texmf-var/web2c
>
> 
- --cnffile /usr/ports/print/tex-xetex/work/fmtutil.cnf;  done fmtutil:
> running `xetex -ini   -jobname=xetex -progname=xetex -etex
> xetex.ini ' ... Shared object "libpoppler.so.44" not found,
> required by "xetex" Error: `xetex -ini  -jobname=xetex
> -progname=xetex -etex xetex.ini ' failed
...

$PATH is incorrect, i.e., newly built xetex must be executed but the
previous binary was executed.  For now, you can manually delete the
two packages and reinstall, e.g.,

pkg delete print/tex-luatex print/tex-xetex
portmaster --no-confirm --no-term-title -D -G \
    print/tex-luatex print/tex-xetex

Jung-uk Kim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJUdMtDAAoJEHyflib82/FGTq0H/iJXyFgtJGy+cBNWD/PXq01D
9xaOPa3L+BjOvvmsbFkVSAcr7AguQOZm8ukVSEX1q6K/7XCPLvWvi42udFbHOcaG
szre4UzBVaHySD2O85sUu/SO1LiBeIlDqNA8AkMApaLN2RjoRPoahuY1TB/8akqK
/fjrLiQYtBigDgzE6Rkmu22Xt5rxTwtHAJSKopjZORYuSbNjQLasBqynv/azxBz/
2mSEyon6QRV0IS519OOoRgvEaA621bUt3wlrnsg1Ir5myjCb/JrrymhnRFMBsKjM
Tz23Uf6R0aOOHD+Nqe8JrJmBVs2hAYFxc6vYWeBkvpyfHCkNrLuamM4ITCgzMFE=
=CYSQ
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Reply via email to