Re: Current amd64 new error or warning from today's current with ruby r320323

On Tue, Jun 27, 2017 at 1:56 PM, Trond Endrestøl < trond.endres...@fagskolen.gjovik.no> wrote: > On Tue, 27 Jun 2017 20:28+0200, Trond Endrestøl wrote: > > > On Sun, 25 Jun 2017 22:05+0300, Konstantin Belousov wrote: > > > > > On Sun, Jun 25, 2017 at 08:51:07PM +0200, Trond Endrest?l wrote: > > >

Re: Current amd64 new error or warning from today's current with ruby r320323

On Tue, 27 Jun 2017 20:28+0200, Trond Endrestøl wrote: > On Sun, 25 Jun 2017 22:05+0300, Konstantin Belousov wrote: > > > On Sun, Jun 25, 2017 at 08:51:07PM +0200, Trond Endrest?l wrote: > > > > https://people.freebsd.org/~kib/misc/vm2.2.patch > > > > > > This patch made ruby23 happy on my end.

Re: Current amd64 new error or warning from today's current with ruby r320323

On Sun, 25 Jun 2017 22:05+0300, Konstantin Belousov wrote: > On Sun, Jun 25, 2017 at 08:51:07PM +0200, Trond Endrest?l wrote: > > > https://people.freebsd.org/~kib/misc/vm2.2.patch > > > > This patch made ruby23 happy on my end. Can't say the same for > > emacs-nox11 or temacs while building

Re: Current amd64 new error or warning from today's current with ruby r320323

On Mon, Jun 26, 2017 at 01:34:35PM -0700, Benno Rice wrote: > > > On Jun 26, 2017, at 13:25, Konstantin Belousov wrote: > > > > On Mon, Jun 26, 2017 at 02:53:14PM -0500, Benjamin Kaduk wrote: > >> On Sun, Jun 25, 2017 at 11:41 AM, Konstantin Belousov >

Re: Current amd64 new error or warning from today's current with ruby r320323

> On Jun 26, 2017, at 13:25, Konstantin Belousov wrote: > > On Mon, Jun 26, 2017 at 02:53:14PM -0500, Benjamin Kaduk wrote: >> On Sun, Jun 25, 2017 at 11:41 AM, Konstantin Belousov >> wrote: >> >>> No need, I understood why MAP_STACK failed in this

Re: Current amd64 new error or warning from today's current with ruby r320323

On Mon, Jun 26, 2017 at 02:53:14PM -0500, Benjamin Kaduk wrote: > On Sun, Jun 25, 2017 at 11:41 AM, Konstantin Belousov > wrote: > > > No need, I understood why MAP_STACK failed in this case, thanks to the > > ktrace log. This is indeed something ruby-specific, or rather,

Re: Current amd64 new error or warning from today's current with ruby r320323

On Sun, Jun 25, 2017 at 11:41 AM, Konstantin Belousov wrote: > No need, I understood why MAP_STACK failed in this case, thanks to the > ktrace log. This is indeed something ruby-specific, or rather, triggered > by ruby special use of libthr. It is not related to the main

Re: Current amd64 new error or warning from today's current with ruby r320323

On Sun, Jun 25, 2017 at 08:51:07PM +0200, Trond Endrest?l wrote: > > https://people.freebsd.org/~kib/misc/vm2.2.patch > > This patch made ruby23 happy on my end. Can't say the same for > emacs-nox11 or temacs while building the former. What exactly do you mean ? Explain the behaviour and show

Re: Current amd64 new error or warning from today's current with ruby r320323

On Sun, 25 Jun 2017 19:41+0300, Konstantin Belousov wrote: > On Sun, Jun 25, 2017 at 08:21:33AM -0700, Manfred Antar wrote: > > > > > On Jun 25, 2017, at 7:50 AM, Konstantin Belousov > > > wrote: > > > > > > On Sun, Jun 25, 2017 at 07:43:25AM -0700, Manfred Antar wrote: >

Re: Current amd64 new error or warning from today's current with ruby r320323

> On Jun 25, 2017, at 10:21 AM, Konstantin Belousov wrote: > > On Sun, Jun 25, 2017 at 10:09:07AM -0700, Manfred Antar wrote: >> >>> On Jun 25, 2017, at 9:41 AM, Konstantin Belousov >>> wrote: >>> >>> On Sun, Jun 25, 2017 at 08:21:33AM -0700,

Re: Current amd64 new error or warning from today's current with ruby r320323

On Sun, Jun 25, 2017 at 10:09:07AM -0700, Manfred Antar wrote: > > > On Jun 25, 2017, at 9:41 AM, Konstantin Belousov > > wrote: > > > > On Sun, Jun 25, 2017 at 08:21:33AM -0700, Manfred Antar wrote: > >> > >>> On Jun 25, 2017, at 7:50 AM, Konstantin Belousov

Re: Current amd64 new error or warning from today's current with ruby r320323

> On Jun 25, 2017, at 9:41 AM, Konstantin Belousov wrote: > > On Sun, Jun 25, 2017 at 08:21:33AM -0700, Manfred Antar wrote: >> >>> On Jun 25, 2017, at 7:50 AM, Konstantin Belousov >>> wrote: >>> >>> On Sun, Jun 25, 2017 at 07:43:25AM -0700, Manfred

Re: Current amd64 new error or warning from today's current with ruby r320323

On Sun, Jun 25, 2017 at 08:21:33AM -0700, Manfred Antar wrote: > > > On Jun 25, 2017, at 7:50 AM, Konstantin Belousov > > wrote: > > > > On Sun, Jun 25, 2017 at 07:43:25AM -0700, Manfred Antar wrote: > >> maybe message got reformatted in mail program (mac mail). > >> could

Re: Current amd64 new error or warning from today's current with ruby r320323

On Sun, 25 Jun 2017 18:08+0200, Trond Endrestøl wrote: > On Sun, 25 Jun 2017 17:56+0200, Trond Endrestøl wrote: > > > On Sun, 25 Jun 2017 17:18+0200, Trond Endrestøl wrote: > > > > > On Sun, 25 Jun 2017 16:41+0300, Konstantin Belousov wrote: > > > > > > > On Sat, Jun 24, 2017 at 07:19:25PM

Re: Current amd64 new error or warning from today's current with ruby r320323

On Sun, 25 Jun 2017 17:56+0200, Trond Endrestøl wrote: > On Sun, 25 Jun 2017 17:18+0200, Trond Endrestøl wrote: > > > On Sun, 25 Jun 2017 16:41+0300, Konstantin Belousov wrote: > > > > > On Sat, Jun 24, 2017 at 07:19:25PM -0700, Manfred Antar wrote: > > > > > > > > > On Jun 24, 2017, at 7:04

Re: Current amd64 new error or warning from today's current with ruby r320323

On Sun, 25 Jun 2017 17:18+0200, Trond Endrestøl wrote: > On Sun, 25 Jun 2017 16:41+0300, Konstantin Belousov wrote: > > > On Sat, Jun 24, 2017 at 07:19:25PM -0700, Manfred Antar wrote: > > > > > > > On Jun 24, 2017, at 7:04 PM, Konstantin Belousov > > > > wrote: > > > >

Re: Current amd64 new error or warning from today's current with ruby r320323

On Sun, 25 Jun 2017 16:41+0300, Konstantin Belousov wrote: > On Sat, Jun 24, 2017 at 07:19:25PM -0700, Manfred Antar wrote: > > > > > On Jun 24, 2017, at 7:04 PM, Konstantin Belousov > > > wrote: > > > > > > On Sat, Jun 24, 2017 at 06:48:03PM -0700, Manfred Antar wrote: >

Re: Current amd64 new error or warning from today's current with ruby r320323

On Sat, Jun 24, 2017 at 07:19:25PM -0700, Manfred Antar wrote: > > > On Jun 24, 2017, at 7:04 PM, Konstantin Belousov > > wrote: > > > > On Sat, Jun 24, 2017 at 06:48:03PM -0700, Manfred Antar wrote: > >> > >>> On Jun 24, 2017, at 6:23 PM, Konstantin Belousov

Re: Current amd64 new error or warning from today's current with ruby r320323

> On Jun 24, 2017, at 7:04 PM, Konstantin Belousov wrote: > > On Sat, Jun 24, 2017 at 06:48:03PM -0700, Manfred Antar wrote: >> >>> On Jun 24, 2017, at 6:23 PM, Konstantin Belousov >>> wrote: >>> >>> On Sat, Jun 24, 2017 at 06:08:50PM -0700, Manfred

Re: Current amd64 new error or warning from today's current with ruby r320323

> On Jun 24, 2017, at 6:55 PM, David Wolfskill wrote: > > On Sat, Jun 24, 2017 at 06:48:03PM -0700, Manfred Antar wrote: >> ... >>> ktrace your failing ruby invocation, then post output of kdump -H somewhere. >>> >> >> Ok not sure if this is right , but this is what i

Re: Current amd64 new error or warning from today's current with ruby r320323

On Sat, Jun 24, 2017 at 06:48:03PM -0700, Manfred Antar wrote: > > > On Jun 24, 2017, at 6:23 PM, Konstantin Belousov > > wrote: > > > > On Sat, Jun 24, 2017 at 06:08:50PM -0700, Manfred Antar wrote: > >> New world and kernel r320323 > >> I get a new error or message when

Re: Current amd64 new error or warning from today's current with ruby r320323

> On Jun 24, 2017, at 6:23 PM, Konstantin Belousov wrote: > > On Sat, Jun 24, 2017 at 06:08:50PM -0700, Manfred Antar wrote: >> New world and kernel r320323 >> I get a new error or message when using ruby: >> >> >> /usr/local/sbin/portupgrade -av >> : warning:

Re: Current amd64 new error or warning from today's current with ruby r320323

On Sat, Jun 24, 2017 at 06:08:50PM -0700, Manfred Antar wrote: > New world and kernel r320323 > I get a new error or message when using ruby: > > > /usr/local/sbin/portupgrade -av > : warning: pthread_create failed for timer: Resource temporarily > unavailable, scheduling broken > >