Re: A reliable port cross-build failure (hangup) in my context (amd64->armv7 cross build, with native-tool speedup involved)

2018-12-24 Thread Mark Millard via freebsd-ports
[A native poudreire-devel based build of multimedia/gstreamer1-qt@qt5 did not hang-up and worked fine. Official package build history also provides some evidence.] On 2018-Dec-22, at 12:55, Mark Millard wrote: > [I found my E-mail records reporting successful builds using > qemu-user-static

Re: SVN r488276 breaks net/qt5-network compilation

2018-12-24 Thread Adriaan de Groot
On Monday, 24 December 2018 18:14:51 CET Michael Butler wrote: > As follows: .. and here I had tested on 11.2 with base SSL, openssl, openssl111, .. and not considered that 12.0 would remove the definition of IFM_FDDI entirely. Fixed, I hope, in r488281 (which built for me in a 12.0-RC3 VM).

SVN r488276 breaks net/qt5-network compilation

2018-12-24 Thread Michael Butler
As follows: --- .obj/qudpsocket.o --- c++ -c -O2 -pipe -march=ivybridge -fstack-protector -fno-strict-aliasing -DOPENSSL_API_COMPAT=0x1010L -std=c++1z -fvisibility=hidden -fvisibility-inlines-hidden -fno-exceptions -Wall -W -Wdate-time -Winconsistent-missing-override -pthread -fPIC

Re: category qt?

2018-12-24 Thread andrew clarke
On Mon 2018-12-24 11:06:56 UTC+0100, Walter Schwarzenfeld (w.schwarzenf...@utanet.at) wrote: > The qt* ports spreads around in the whole portstree. > > It is reasonable to concentrate all these ports in a qt category? I think it > is easier to find (and also easier to maintain). Why? You'd

Re: category qt?

2018-12-24 Thread Adriaan de Groot
On Monday, 24 December 2018 13:00:02 CET freebsd-ports-requ...@freebsd.org wrote: > > The qt* ports spreads around in the whole portstree. > > > > It is reasonable to concentrate all these ports in a qt category? I > > think it is easier to find (and also easier to maintain). > > Indeed it is a

Re: category qt?

2018-12-24 Thread Mathieu Arnold
On Mon, Dec 24, 2018 at 11:06:56AM +0100, Walter Schwarzenfeld wrote: > The qt* ports spreads around in the whole portstree. > > It is reasonable to concentrate all these ports in a qt category? I think it > is easier to find (and also easier to maintain). While a virtual category could easily

Re: texlive-texmf

2018-12-24 Thread starikarp
On Mon, 24 Dec 2018 15:50:23 +0300 wrote: > On Sun, 23 Dec 2018 19:01:15 -0500 > wrote: > > > Hi! > > > > I try to install libreoffice and it pulls also > > texlive-texmf which size is about 2 GB and I have a slow > > Internet. After was done, please read bellow. > > > > => Fetching all

Re: texlive-texmf

2018-12-24 Thread graahnul.grom
On Sun, 23 Dec 2018 19:01:15 -0500 wrote: > Hi! > > I try to install libreoffice and it pulls also > texlive-texmf which size is about 2 GB and I have a slow > Internet. After was done, please read bellow. > > => Fetching all distfiles required by > texlive-texmf-20150523_4 for building ===>

FreeBSD ports you maintain which are out of date

2018-12-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,

Re: category qt?

2018-12-24 Thread Lorenzo Salvadore via freebsd-ports
> The qt* ports spreads around in the whole portstree. > > It is reasonable to concentrate all these ports in a qt category? I > think it is easier to find (and also easier to maintain). Indeed it is a bit annoying for me when I have to update qt* ports. I don't use portmaster or similar (I don't

category qt?

2018-12-24 Thread Walter Schwarzenfeld
The qt* ports spreads around in the whole portstree. It is reasonable to concentrate all these ports in a qt category? I think it is easier to find (and also easier to maintain). ___ freebsd-ports@freebsd.org mailing list