Re: qt5 fails to build

2017-02-22 Thread Walter Schwarzenfeld
It still fails with the same error after r434635. (changed the patch in the PR). ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: qt5 fails to build

2017-02-20 Thread tech-lists
On 19/02/2017 20:44, Walter Schwarzenfeld wrote: > Have the same problem. (Maybe, it is a problem with libressl) > Make this PR > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217220 added your patch, recompiled & installed fine. Then I redid qt5-core, then devel/qt5 and it's all ok now :D m

Re: qt5 fails to build

2017-02-19 Thread Walter Schwarzenfeld
Have the same problem. (Maybe, it is a problem with libressl) Make this PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217220 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send

Re: qt5 fails to build

2017-02-19 Thread John
Hi, On Sun, 19 Feb 2017, at 19:46, Marco Beishuizen wrote: > On Sun, 19 Feb 2017, the wise tech-lists wrote: > > > I'm trying to build qt5 on a fresh freebsd-11-stable image. If it works, > > then there's something wrong with ports on my desktop. > > I've just upgraded qt5 on my FreeBSD 11-ST m

Re: qt5 fails to build

2017-02-19 Thread Marco Beishuizen
On Sun, 19 Feb 2017, the wise tech-lists wrote: I'm trying to build qt5 on a fresh freebsd-11-stable image. If it works, then there's something wrong with ports on my desktop. I've just upgraded qt5 on my FreeBSD 11-ST machine with portupgrade. In general it went fine. Only hickup was that "q

Re: qt5 fails to build

2017-02-19 Thread Raphael Kubo da Costa
tech-lists writes: > On 19/02/2017 13:56, Raphael Kubo da Costa wrote: > >> tech-lists writes: >> >>> Shall I try building qt5-concurrent again? >> >> Yes, please. > > still failing, unfortunately. I've posted the script log here: > > http://www.zyxst.net/~bofh/logs/qt5c6.txt /usr/local/bin/l

Re: qt5 fails to build

2017-02-19 Thread Kevin Oberman
On Sun, Feb 19, 2017 at 7:20 AM, tech-lists wrote: > On 19/02/2017 13:56, Raphael Kubo da Costa wrote: > > tech-lists writes: > > > >> Shall I try building qt5-concurrent again? > > > > Yes, please. > > I'm trying to build qt5 on a fresh freebsd-11-stable image. If it works, > then there's somet

Re: qt5 fails to build

2017-02-19 Thread tech-lists
On 19/02/2017 13:56, Raphael Kubo da Costa wrote: > tech-lists writes: > >> Shall I try building qt5-concurrent again? > > Yes, please. I'm trying to build qt5 on a fresh freebsd-11-stable image. If it works, then there's something wrong with ports on my desktop. -- J. ___

Re: qt5 fails to build

2017-02-19 Thread tech-lists
On 19/02/2017 13:56, Raphael Kubo da Costa wrote: > tech-lists writes: > >> Shall I try building qt5-concurrent again? > > Yes, please. still failing, unfortunately. I've posted the script log here: http://www.zyxst.net/~bofh/logs/qt5c6.txt -- J.

Re: qt5 fails to build

2017-02-19 Thread Raphael Kubo da Costa
tech-lists writes: > Shall I try building qt5-concurrent again? Yes, please. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: qt5 fails to build

2017-02-19 Thread tech-lists
On 19/02/2017 13:12, Raphael Kubo da Costa wrote: > Hmm, the -qtconf option that it's complaining about was introduced in Qt > 5.7.0. devel/qt5-qmake should have been updated automatically before > qt5-concurrent. > > Can you make sure qt5-qmake (which used to be called devel/qmake5) is at > 5.7.1

Re: qt5 fails to build

2017-02-19 Thread Raphael Kubo da Costa
tech-lists writes: > On 19/02/2017 13:01, Raphael Kubo da Costa wrote: > >> The output looks like Qt4's qmake, not Qt5's. Can you run >> "/storage/usr/ports/devel/qt5-concurrent/work/qtbase-opensource-src-5.7.1/bin/qmake >> -v" and paste the output? > > # > /storage/usr/ports/devel/qt5-concurrent

Re: qt5 fails to build

2017-02-19 Thread tech-lists
On 19/02/2017 13:01, Raphael Kubo da Costa wrote: > The output looks like Qt4's qmake, not Qt5's. Can you run > "/storage/usr/ports/devel/qt5-concurrent/work/qtbase-opensource-src-5.7.1/bin/qmake > -v" and paste the output? # /storage/usr/ports/devel/qt5-concurrent/work/qtbase-opensource-src-5.7.1

Re: qt5 fails to build

2017-02-19 Thread Raphael Kubo da Costa
tech-lists writes: > Hi, here's the output: > > # pwd > /storage/usr/ports/devel/qt5-concurrent > > # make WANT_QT_VERBOSE_CONFIGURE=YES > ***Unknown option -qtconf > Usage: > /storage/usr/ports/devel/qt5-concurrent/work/qtbase-opensource-src-5.7.1/bin/qmake > [mode] [options] [files] The output

Re: qt5 fails to build

2017-02-19 Thread tech-lists
On 19/02/2017 12:39, Raphael Kubo da Costa wrote: > tech-lists writes: > >> Hi, >> >> On 19/02/2017 11:51, Raphael Kubo da Costa wrote: >> >>> Can you send config.log to the list? From the error message it's not >>> clear what exactly is wrong with the mkspec, of if the problem's really >>> with

Re: qt5 fails to build

2017-02-19 Thread Raphael Kubo da Costa
tech-lists writes: > Hi, > > On 19/02/2017 11:51, Raphael Kubo da Costa wrote: > >> Can you send config.log to the list? From the error message it's not >> clear what exactly is wrong with the mkspec, of if the problem's really >> with the mkspec at all. > > Weirder and weirder. There is no confi

Re: qt5 fails to build

2017-02-19 Thread tech-lists
Hi, On 19/02/2017 11:51, Raphael Kubo da Costa wrote: > Can you send config.log to the list? From the error message it's not > clear what exactly is wrong with the mkspec, of if the problem's really > with the mkspec at all. Weirder and weirder. There is no config.log present. Here is the outpu

Re: qt5 fails to build

2017-02-19 Thread Raphael Kubo da Costa
tech-lists writes: > Running configuration tests... > Failed to process makespec for platform > '/usr/local/lib/qt5/mkspecs/freebsd-clang' > > Turn on verbose messaging (-v) to see the final report. > > ===> Script "configure" failed unexpectedly. > Please report the problem to k...@freebsd.org [m