Solved print/tex-xetex-0.99993_5 fails to build

[mkernalcon]

Hi,

For a little while now, I've been unable to upgrade tex-xetex from 0.99993_4 to _5, due to a build error. Relevantly:

/bin/cat /usr/ports/print/tex-xetex/work/fmtutil.cnf |  while read format dum; do  /usr/bin/env PATH=/usr/ports/print/tex-xetex/work/stage/usr/local/bin:/usr/ports/print/tex-xetex/work/.bin:/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/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: fmtutil is using the following fmtutil.cnf files (in precedence order):
fmtutil:   /usr/ports/print/tex-xetex/work/fmtutil.cnf
fmtutil: fmtutil is using the following fmtutil.cnf file for writing changes:
fmtutil:   /usr/ports/print/tex-xetex/work/fmtutil.cnf
fmtutil [INFO]: writing formats under /usr/ports/print/tex-xetex/work/stage/usr/local/share/texmf-var/web2c
fmtutil [INFO]: --- remaking xetex with xetex
fmtutil: running `xetex -ini   -jobname=xetex -progname=xetex -etex xetex.ini' ...
ld-elf.so.1: Shared object "libicui18n.so.73" not found, required by "xetex"
fmtutil [INFO]: log file copied to: /usr/ports/print/tex-xetex/work/stage/usr/local/share/texmf-var/web2c/xetex/xetex.log
fmtutil [ERROR]: running `xetex -ini   -jobname=xetex -progname=xetex -etex xetex.ini </dev/null' return status: 1
fmtutil [ERROR]: returning error due to option --strict
fmtutil [INFO]: not selected formats: 3
fmtutil [INFO]: failed to build: 1 (xetex/xetex)
fmtutil [INFO]: total formats: 4
fmtutil [INFO]: exiting with status 1
*** Error code 1

Stop.
make: stopped in /usr/ports/print/tex-xetex

My devel/icu is at 74.1,1, and I have since rebuilt everything that requires icu (using portmaster -r icu). I've also tried running make clean in the tex-xetex ports directory and building again, to the same result. Due to the version change, I have libicui18n.so.74 (and with an extra .1, and without the .74), but obviously not .73.

Is this a problem with my environment, or shall I post a bug report? Any idea of a solution?

Thanks in advance.

 

[SirDice]

Is this a problem with my environment, or shall I post a bug report?

Go to the Freshports page: print/tex-xetex. Click on the "radioactive" button next to the port name. It will lead you here: https://portsfallout.com/fallout?port=print/tex-xetex$

That page will tell you if the FreeBSD build clusters have issues building the port. Or not, in this case. If the build clusters don't have the same problem as you then you can be pretty sure the issue is caused by something local.

Another option is to lookup the build logs, but that can be a bit tricky, the interface is rather daunting. https://pkg-status.freebsd.org/builds?jailname=132amd64

Quarterly still has _4, but latest does have a complete build for _5. This is the build log: http://beefy16.nyi.freebsd.org/data/132amd64-default/c5a12469a2ad/logs/tex-xetex-0.99993_5.log (you need IPv6 to access it though).

 

[mkernalcon]

Thanks, those are extremely helpful, and I will save this in my documentation to check for future issues. I did figure that this was a problem with my system, not generally, hence why I posted here first rather than bugzilla.

In any case, I finally cracked it: the install stage for tex-xetex used the previously installed xetex binary to complete some of its steps - obviously the previous version was built against icu 73, and so was not able to run. By first uninstalling tex-xetex, it forced the port to use the xetex binary that it built instead of the system one, and was able to complete successfully.

Feels like this should have been an entry in /usr/ports/UPDATING, but I'm just glad I finally got this taken care of.