Re: qemu-arm-static under amd64: example of stuck looping atomic_cmpset_int while building graphics/poppler-qt5 [a tested fix included]

2019-01-02 Thread Mark Millard via freebsd-ports
On 2019-Jan-2, at 17:41, Kyle Evans wrote: > On Wed, Jan 2, 2019 at 3:38 AM Mark Millard via freebsd-ports > wrote: >> >>> . . . >> >> So (without old line numbers): >> >>} else if (TARGET_URWLOCK_READER_COUNT(state) != 0) { >>/* decrement reader count */ >>for (;;) { >>

Re: qemu-arm-static under amd64: example of stuck looping atomic_cmpset_int while building graphics/poppler-qt5 [a tested fix included]

2019-01-02 Thread Kyle Evans
On Wed, Jan 2, 2019 at 3:38 AM Mark Millard via freebsd-ports wrote: > > On 2019-Jan-1, at 18:43, Mark Millard wrote: > > > The below showed up for poudiere-devel bulk getting stuck using one FreeBSD > > cpu while building graphics/poppler-qt5 . This is not a kevent hang-up, > > unlike > > the l

Re: sysutils/915resolution

2019-01-02 Thread Niclas Zeising
On 2019-01-02 16:37, Matthias Apitz wrote: El día miércoles, enero 02, 2019 a las 04:24:09p. m. +0100, Niclas Zeising escribió: On 2019-01-02 14:09, Matthias Apitz wrote: Hello, I've updated a FreeBSD on an Acer C720 laptop to 13.0-CURRENT (r342378) and port sysutils/915resolution to r48823

Re: sysutils/915resolution

2019-01-02 Thread Matthias Apitz
El día miércoles, enero 02, 2019 a las 04:24:09p. m. +0100, Niclas Zeising escribió: > On 2019-01-02 14:09, Matthias Apitz wrote: > > > > Hello, > > > > I've updated a FreeBSD on an Acer C720 laptop to 13.0-CURRENT (r342378) > > and port sysutils/915resolution to r488233. This says now on boot:

Re: sysutils/915resolution

2019-01-02 Thread Niclas Zeising
On 2019-01-02 14:09, Matthias Apitz wrote: Hello, I've updated a FreeBSD on an Acer C720 laptop to 13.0-CURRENT (r342378) and port sysutils/915resolution to r488233. This says now on boot: Jan 1 07:06:41 c720-r342378 kernel: Intel chipset detected. However, 915resolution was unable to d

Re: vim - GTK2 or GTK3?

2019-01-02 Thread Niclas Zeising
On 2019-01-02 10:42, Lars Engels wrote: On Tue, Jan 01, 2019 at 01:07:24PM -0700, Adam Weinberger wrote: I'm curious whether the default Vim port should use GTK2 or GTK3 as its UI toolkit, but I use neither so I need input from people here. Right now it defaults to GTK2, but I'm suspecting that

FreeBSD ports you maintain which are out of date

2019-01-02 Thread portscout
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you

sysutils/915resolution

2019-01-02 Thread Matthias Apitz
Hello, I've updated a FreeBSD on an Acer C720 laptop to 13.0-CURRENT (r342378) and port sysutils/915resolution to r488233. This says now on boot: Jan 1 07:06:41 c720-r342378 kernel: Intel chipset detected. However, 915resolution was unable to determine the chipset type. Jan 1 07:06:41

Re: vim - GTK2 or GTK3?

2019-01-02 Thread Lars Engels
On Tue, Jan 01, 2019 at 01:07:24PM -0700, Adam Weinberger wrote: > I'm curious whether the default Vim port should use GTK2 or GTK3 as > its UI toolkit, but I use neither so I need input from people here. > > Right now it defaults to GTK2, but I'm suspecting that more people use > GTK3 these days.

Re: qemu-arm-static under amd64: example of stuck looping atomic_cmpset_int while building graphics/poppler-qt5 [a tested fix included]

2019-01-02 Thread Mark Millard via freebsd-ports
On 2019-Jan-1, at 18:43, Mark Millard wrote: > The below showed up for poudiere-devel bulk getting stuck using one FreeBSD > cpu while building graphics/poppler-qt5 . This is not a kevent hang-up, unlike > the last hang-up that I analyzed. I do not yet know how repeatable this is > but the origin