Hmm. I built/installed xorg-libXt +flat_namespace as part of migrating my work MBP to High Sierra yesterday. There must be some underlying issue here.
> On Nov 19, 2017, at 2:26 PM, Richard L. Hamilton <[email protected]> wrote: > > > >> On Nov 19, 2017, at 14:35, Ryan Schmidt <[email protected]> wrote: >> >> >> On Nov 19, 2017, at 09:27, Richard L. Hamilton wrote: >> >>> Reinstalling after migrating to High Sierra, it had to be that something >>> wouldn't rebuild, and this was it. xorg-libXt won't build because the >>> xsltproc processes never finish. For giggles, I temporarily swapped the >>> one already in /opt/local/bin with the somewhat older binary supplied by >>> Apple, and it did the same...leading me to suppose that although they >>> perhaps shouldn't behave that way, it's something in the input they're fed >>> that has them running indefinitely (and using all the CPU they can get >>> while they're doing it, too). >>> >>> Ideas? >> >> Hmm, not really. xorg-libXt built fine on High Sierra on our build system in >> September. https://packages.macports.org/xorg-libXt/ (You cannot use our >> binaries?) > > > Don't I need a build with +flat_namespace if I'm going to link with OpenMotif? > Marius -- Marius Schamschula
