X11 breaks for Intel after ports update from r433396 -> r433935?

[Matthew D. Fuller]

On Sun, Feb 12, 2017 at 06:35:08PM -0800 I heard the voice of
David Wolfskill, and lo! it spake thus:
>
> and that's how I found out that X11 appears to be broken now.

You don't include the salient bits of the actual X log showing the
failure.  So I'm gonna assume it's the same thing I've seen on 2
machines now, and somebody else mentions in
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214591#c12>

Specifically, to take a bit of a handy Xorg.0.log from my workstation:

[   149.338] (EE).
[   149.338] (EE) Backtrace:
[...]
[   149.354] (EE) 7: /usr/local/llvm39/lib/libLLVM-3.9.so (_ZN4llvm2cl6Option11addArgumentEv+0x7c) [0x809876e8c]
[   149.361] (EE) 8: /usr/local/llvm34/lib/libLLVM-3.4.so (_ZN4llvm16PPCTargetMachine17addAnalysisPassesERNS_6legacy15PassManagerBaseE+0x262) [0x80e3901e2]
[...]
[   149.375] (EE) 22: /usr/local/bin/X (_start+0x17f) [0x42507f]
[   149.376] (EE) 23: ? (?+0x17f) [0x80083117f]
[   149.376] (EE).
[   149.376] (EE) Segmentation fault at address 0x0

It's a pretty good bet that pulling in bits of libLLVM 3.4 and 3.9
simultaneously is gonna be Really Bad.  The first machine only had the
LLVM 3.7 that X was previously using, and the new 3.9; uninstalling
3.7 made it just pick up working.  On my workstation, I've got 3.4
onward all installed for testing some stuff, so when I temporarily
uninstalled 3.4 after the above, it helpfully blew up on 3.5 instead.
So I wound up having to stash away and pull off everything but 3.9,
starting X, then re-installing them.


Something in the X server is getting too durn adventurous looking for
stuff to link in.



-- 
Matthew Fuller     (MF4839)   |  fullermd at over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.