Re: nginx is not linking against libressl

2017-05-12 Thread abi
On 11.05.2017 04:58, Adam Weinberger wrote: On 10 May, 2017, at 18:42, Sergey A. Osokin wrote: On Wed, May 10, 2017 at 11:13:05PM +, Sergey A. Osokin wrote: On Wed, May 10, 2017 at 10:56:26PM +, Sergey A. Osokin wrote: On Wed, May 10, 2017 at 04:04:52PM -0600, Adam Weinberger wrote:

Re: Xrdp help needed

2017-05-12 Thread Wojciech Puchar
How xorgxrdp doesn't work? logs in and black screen. Xorg process is there. relogging - again black screen. -- `whois vmeta.jp | nkf -w` meta ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To u

Re: www/firefox on RPI2: error: instruction requires: armv6t2

2017-05-12 Thread bob prohaska
On Thu, May 11, 2017 at 08:14:14PM -0700, Mark Millard wrote: > Having -mcpu=cortex-a7 in ASFLAGS would contribute to > both of the examples. > Restarting the make with root@www:/usr/ports/www/firefox # make CFLAGS=-mcpu=cortex-a7 ASFLAGS=-mcpu=cortex-a7 -DBATCH > & make.log & made considerably

Re: www/firefox on RPI2: error: instruction requires: armv6t2

2017-05-12 Thread Mark Millard
On 2017-May-12, at 12:31 PM, bob prohaska wrote: > On Thu, May 11, 2017 at 08:14:14PM -0700, Mark Millard wrote: >> Having -mcpu=cortex-a7 in ASFLAGS would contribute to >> both of the examples. >> > > Restarting the make with > root@www:/usr/ports/www/firefox # make CFLAGS=-mcpu=cortex-a7 > A

Re: www/firefox on RPI2: error: instruction requires: armv6t2

2017-05-12 Thread bob prohaska
On Fri, May 12, 2017 at 02:36:48PM -0700, Mark Millard wrote: > > My guess from the above is that the problem will > repeat in this rebuild. > > > That's exactly what happened. A copy of make.log and armSP_FFTInv_CCSToR_F32_preTwiddleRadix2_unsafe_s.S can be found at http://www.zefox.net/~

Re: www/firefox on RPI2: error: instruction requires: armv6t2

2017-05-12 Thread Mark Millard
On 2017-May-12, at 5:34 PM, bob prohaska wrote: > On Fri, May 12, 2017 at 02:36:48PM -0700, Mark Millard wrote: >> >> My guess from the above is that the problem will >> repeat in this rebuild. >> >> >> > That's exactly what happened. A copy of make.log and > > armSP_FFTInv_CCSToR_F32_pre