re: xsrc/54265: X with MKLLVMRT=no not working

[matthew green <mrg%eterna.com.au@localhost>]

The following reply was made to PR xsrc/54265; it has been noted by GNATS.

From: matthew green <mrg%eterna.com.au@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: xsrc-manager%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
    netbsd-bugs%netbsd.org@localhost
Subject: re: xsrc/54265: X with MKLLVMRT=no not working
Date: Tue, 04 Jun 2019 14:58:46 +1000

 hmm, there's nothing in the log that would indicate what went
 wrong, it is as if the clients all went away and it exited..
 
 can you try ktrace or some additional logging to see what is
 happening?
 
 > I did a local build with MKLLVMRT=3Dno, thinking my machine would not be=
  affected
 > by the lost functionality (X log never mentioned AMDGPU or similar).
 > =
 
 > But the resulting system can not start X at all.
 > =
 
 > radeon0 at pci1 dev 0 function 0: vendor 1002 product 68e0 (rev. 0x00)
 > kern info: [drm] initializing kernel modesetting (CEDAR 0x1002:0x68E0 0x=
 1025:0x0347).
 
 i don't understand the comment about AMDGPU here.  all radeon
 (and unsupported amdgpu) will be affected by MKLLVMRT=3Dno.
 
 for me, it meant GL is slow, but Xvideo is there, so while it
 can't do "mpv -vo gpu" well, it can do "mpv -vo xv" fine.
 
 
 .mrg.