Re: LLVM target 'amdgpu' not enabled Was: Re: Conflict on very first port (xorg) on rpi3

2020-05-16 Thread bob prohaska
On Sat, May 16, 2020 at 06:08:13PM +0200, Dimitry Andric wrote: > On 16 May 2020, at 17:44, bob prohaska wrote: > > > > Deinstalling the conflicting port made considerable progress toward a build > > of > > x11/xorg, but now make is stopping with: > > > > configure: error: LLVM target 'amdgpu'

Re: LLVM target 'amdgpu' not enabled Was: Re: Conflict on very first port (xorg) on rpi3

2020-05-16 Thread Dimitry Andric
On 16 May 2020, at 17:44, bob prohaska wrote: > > Deinstalling the conflicting port made considerable progress toward a build of > x11/xorg, but now make is stopping with: > > configure: error: LLVM target 'amdgpu' not enabled in your LLVM build. > Required by radv. > > I've tried turning off

LLVM target 'amdgpu' not enabled Was: Re: Conflict on very first port (xorg) on rpi3

2020-05-16 Thread bob prohaska
Deinstalling the conflicting port made considerable progress toward a build of x11/xorg, but now make is stopping with: configure: error: LLVM target 'amdgpu' not enabled in your LLVM build. Required by radv. I've tried turning off Wayland support in graphics/mesa-dri but that didn't help. Si

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Mark Millard via freebsd-ports
On 2020-May-15, at 13:03, bob prohaska wrote: > On Fri, May 15, 2020 at 12:33:02PM -0700, Mark Millard wrote: >> [Gack: devel/cmake needs devel/py-sphinx by default >> and devel/llvm80 needs both devel/cmake and >> devel/py-pshinx18 by default.] >> >> On 2020-May-15, at 11:59, Mark Millard w

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread bob prohaska
On Fri, May 15, 2020 at 12:33:02PM -0700, Mark Millard wrote: > [Gack: devel/cmake needs devel/py-sphinx by default > and devel/llvm80 needs both devel/cmake and > devel/py-pshinx18 by default.] > > On 2020-May-15, at 11:59, Mark Millard wrote: > > > > On 2020-May-15, at 11:05, bob prohaska wro

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Chris
On Fri, 15 May 2020 11:05:54 -0700 bob prohaska f...@www.zefox.net said On Fri, May 15, 2020 at 01:49:21PM -0300, Danilo G. Baio wrote: > On Fri, May 15, 2020 at 08:19:22AM -0700, bob prohaska wrote: > > On Fri, May 15, 2020 at 12:33:10AM -0700, Mark Millard via freebsd-ports > wrote: > > > > >

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Mark Millard via freebsd-ports
[Gack: devel/cmake needs devel/py-sphinx by default and devel/llvm80 needs both devel/cmake and devel/py-pshinx18 by default.] On 2020-May-15, at 11:59, Mark Millard wrote: > > On 2020-May-15, at 11:05, bob prohaska wrote: > >> On Fri, May 15, 2020 at 01:49:21PM -0300, Danilo G. Baio wrote: >>

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Mark Millard via freebsd-ports
On 2020-May-15, at 11:05, bob prohaska wrote: > On Fri, May 15, 2020 at 01:49:21PM -0300, Danilo G. Baio wrote: >> On Fri, May 15, 2020 at 08:19:22AM -0700, bob prohaska wrote: >>> On Fri, May 15, 2020 at 12:33:10AM -0700, Mark Millard via freebsd-ports >>> wrote: Some building and is

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread bob prohaska
On Fri, May 15, 2020 at 01:49:21PM -0300, Danilo G. Baio wrote: > On Fri, May 15, 2020 at 08:19:22AM -0700, bob prohaska wrote: > > On Fri, May 15, 2020 at 12:33:10AM -0700, Mark Millard via freebsd-ports > > wrote: > > > > > > Some building and isntalling had to occur prior to the > > > textproc

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Danilo G. Baio
On Fri, May 15, 2020 at 08:19:22AM -0700, bob prohaska wrote: > On Fri, May 15, 2020 at 12:33:10AM -0700, Mark Millard via freebsd-ports > wrote: > > > > Some building and isntalling had to occur prior to the > > textproc/py-sphinx18 build attempt, possibly from > > prior session(s) of building a

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Mark Millard via freebsd-ports
On 2020-May-15, at 08:19, bob prohaska wrote: > On Fri, May 15, 2020 at 12:33:10AM -0700, Mark Millard via freebsd-ports > wrote: >> >> Some building and isntalling had to occur prior to the >> textproc/py-sphinx18 build attempt, possibly from >> prior session(s) of building and installing.

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread bob prohaska
On Fri, May 15, 2020 at 12:33:10AM -0700, Mark Millard via freebsd-ports wrote: > > Some building and isntalling had to occur prior to the > textproc/py-sphinx18 build attempt, possibly from > prior session(s) of building and installing. > > In this case x11/xorg was the first port attempted in

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Mark Millard via freebsd-ports
On 2020-May-15, at 00:33, Mark Millard wrote: > bob prohaska fbsd at www.zefox.net wrote on > Fri May 15 04:30:07 UTC 2020 : > >> An attempt to compile x11/xorg on a new installation of 12.1 on a Pi3B >> resulted in a >> conflict: >> >> ===> Installing for py37-sphinx18-1.8.5_1,1 >> ===>

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Mark Millard via freebsd-ports
bob prohaska fbsd at www.zefox.net wrote on Fri May 15 04:30:07 UTC 2020 : > An attempt to compile x11/xorg on a new installation of 12.1 on a Pi3B > resulted in a > conflict: > > ===> Installing for py37-sphinx18-1.8.5_1,1 > ===> Checking if py37-sphinx18 is already installed > ===> Registe

Conflict on very first port (xorg) on rpi3

2020-05-14 Thread bob prohaska
An attempt to compile x11/xorg on a new installation of 12.1 on a Pi3B resulted in a conflict: ===> Installing for py37-sphinx18-1.8.5_1,1 ===> Checking if py37-sphinx18 is already installed ===> Registering installation for py37-sphinx18-1.8.5_1,1 as automatic Installing py37-sphinx18-1.8.