Re: powerpc64 graphics/mesa-dri build failure in poudriere, system clang's /usr/bin/cc got assert failure: "Target supports vector op, but scalar requires expansion?"

2019-05-24 Thread Ralf Wenk
On 2019-05-23, at 12:31 -0700, Mark Millard wrote: > On 2019-May-23, at 11:47, Jan Beich wrote: > > > Mark Millard writes: > > > >> Unfortunately poudiere bulk tar archives of failures do not > >> catch the /tmp/* material from: > >> > >> cc: error: unable to execute command: Abort trap (core

Re: powerpc64 graphics/mesa-dri build failure in poudriere, system clang's /usr/bin/cc got assert failure: "Target supports vector op, but scalar requires expansion?"

2019-05-24 Thread Mark Millard via freebsd-ports
On 2019-May-24, at 00:10, Ralf Wenk wrote: > On 2019-05-23, at 12:31 -0700, Mark Millard wrote: >> On 2019-May-23, at 11:47, Jan Beich wrote: >> >>> Mark Millard writes: >>> Unfortunately poudiere bulk tar archives of failures do not catch the /tmp/* material from: cc:

FreeBSD ports you maintain which are out of date

2019-05-24 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

Policy on closing bugs

2019-05-24 Thread Grzegorz Junka
Hey, Is there any policy/document when a bug can be closed? For example, is it OK to close a bug that is fixed upstream but not yet in ports? Thanks GrzegorzJ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/fre

Re: powerpc64 graphics/mesa-dri build failure in poudriere, system clang's /usr/bin/cc got assert failure: "Target supports vector op, but scalar requires expansion?"

2019-05-24 Thread Jan Beich
Ralf Wenk writes: > On 2019-05-23, at 12:31 -0700, Mark Millard wrote: > >> On 2019-May-23, at 11:47, Jan Beich wrote: >> >> > Mark Millard writes: >> > >> >> Unfortunately poudiere bulk tar archives of failures do not >> >> catch the /tmp/* material from: >> >> >> >> cc: error: unable to ex

Re: Policy on closing bugs

2019-05-24 Thread Jan Bramkamp
On 24.05.19 12:07, Grzegorz Junka wrote: Hey, Is there any policy/document when a bug can be closed? For example, is it OK to close a bug that is fixed upstream but not yet in ports? Thanks GrzegorzJ I don't know of any official policy, but as a user (and port maintainer) I would prefer an

Re: Policy on closing bugs

2019-05-24 Thread Grzegorz Junka
On 24/05/2019 10:53, Jan Bramkamp wrote: On 24.05.19 12:07, Grzegorz Junka wrote: Hey, Is there any policy/document when a bug can be closed? For example, is it OK to close a bug that is fixed upstream but not yet in ports? Thanks GrzegorzJ I don't know of any official policy, but as a user

Re: Policy on closing bugs

2019-05-24 Thread Kubilay Kocak
On 24/05/2019 8:07 pm, Grzegorz Junka wrote: Hey, Is there any policy/document when a bug can be closed? For example, is it OK to close a bug that is fixed upstream but not yet in ports? Thanks GrzegorzJ Hi Grzegorz, Bugs are closed after they are "resolved". Resolved means a resolution

Re: Policy on closing bugs

2019-05-24 Thread Grzegorz Junka
On 24/05/2019 11:12, Kubilay Kocak wrote: On 24/05/2019 8:07 pm, Grzegorz Junka wrote: Hey, Is there any policy/document when a bug can be closed? For example, is it OK to close a bug that is fixed upstream but not yet in ports? Thanks GrzegorzJ Hi Grzegorz, Bugs are closed after they

Re: Policy on closing bugs

2019-05-24 Thread Grzegorz Junka
On 24/05/2019 11:30, Grzegorz Junka wrote: On 24/05/2019 11:12, Kubilay Kocak wrote: On 24/05/2019 8:07 pm, Grzegorz Junka wrote: Hey, Is there any policy/document when a bug can be closed? For example, is it OK to close a bug that is fixed upstream but not yet in ports? Thanks GrzegorzJ

Re: Policy on closing bugs

2019-05-24 Thread Kubilay Kocak
On 24/05/2019 9:30 pm, Grzegorz Junka wrote: On 24/05/2019 11:12, Kubilay Kocak wrote: On 24/05/2019 8:07 pm, Grzegorz Junka wrote: Hey, Is there any policy/document when a bug can be closed? For example, is it OK to close a bug that is fixed upstream but not yet in ports? Thanks GrzegorzJ

Re: Policy on closing bugs

2019-05-24 Thread Kubilay Kocak
On 24/05/2019 9:52 pm, Grzegorz Junka wrote: On 24/05/2019 11:30, Grzegorz Junka wrote: On 24/05/2019 11:12, Kubilay Kocak wrote: On 24/05/2019 8:07 pm, Grzegorz Junka wrote: Hey, Is there any policy/document when a bug can be closed? For example, is it OK to close a bug that is fixed upst

Re: Policy on closing bugs

2019-05-24 Thread Grzegorz Junka
On 24/05/2019 12:34, Kubilay Kocak wrote: On 24/05/2019 9:52 pm, Grzegorz Junka wrote: On 24/05/2019 11:30, Grzegorz Junka wrote: On 24/05/2019 11:12, Kubilay Kocak wrote: On 24/05/2019 8:07 pm, Grzegorz Junka wrote: Hey, Is there any policy/document when a bug can be closed? For exampl

Re: Policy on closing bugs

2019-05-24 Thread Kubilay Kocak
On 24/05/2019 10:45 pm, Grzegorz Junka wrote: On 24/05/2019 12:34, Kubilay Kocak wrote: On 24/05/2019 9:52 pm, Grzegorz Junka wrote: On 24/05/2019 11:30, Grzegorz Junka wrote: On 24/05/2019 11:12, Kubilay Kocak wrote: On 24/05/2019 8:07 pm, Grzegorz Junka wrote: Hey, Is there any policy/

Re: Policy on closing bugs

2019-05-24 Thread Grzegorz Junka
On 24/05/2019 12:48, Kubilay Kocak wrote: On 24/05/2019 10:45 pm, Grzegorz Junka wrote: On 24/05/2019 12:34, Kubilay Kocak wrote: On 24/05/2019 9:52 pm, Grzegorz Junka wrote: On 24/05/2019 11:30, Grzegorz Junka wrote: On 24/05/2019 11:12, Kubilay Kocak wrote: On 24/05/2019 8:07 pm, Grze

Re: Policy on closing bugs

2019-05-24 Thread Grzegorz Junka
On 24/05/2019 12:26, Kubilay Kocak wrote: On 24/05/2019 9:30 pm, Grzegorz Junka wrote: On 24/05/2019 11:12, Kubilay Kocak wrote: On 24/05/2019 8:07 pm, Grzegorz Junka wrote: Hey, Is there any policy/document when a bug can be closed? For example, is it OK to close a bug that is fixed upst

net/rtg committer needed

2019-05-24 Thread Andrew
Hi, net/rtg no longer runs on modern perl. The maintainer made a patch almost a year ago, but it's been stalled on some flavour stuff. I've modified the patch to remove the offending flavour bits, but haven't heard back from the maintainer in almost a month, even tried poking him out of ban

Re: powerpc64 system-clang-8 based context: x11-toolkits/qt5-declarative fails to build in poudriere: /usr/local/lib/qt5/bin/qlalr segmentation faults in std::type_info::~type_info() () from /usr/loca

2019-05-24 Thread Mark Millard via freebsd-ports
On 2019-May-24, at 11:25, Mark Linimon wrote: > On Thu, May 23, 2019 at 10:33:35PM -0700, Mark Millard via freebsd-toolchain > wrote: >> That is no matter what the system compiler is for powerpc64. >> >> This lead to the below mixing of libstdc++.so.6 and libc++/libcxxrt . . . > > Yeah. This

new port: game/dMagnetic (moved to github, and help needed)

2019-05-24 Thread dettus
You wake up on a sunny August morning with birds singing, and the air fresh and clear. However, your joints are stiff and you have not woken up in your bedroom as you would have expected. Trying to recall what happened the night before, you manage to piece together a few brief glimpses to give