FreeBSD ports you maintain which are out of date

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

RE: maintenance of gcc cross ports

2019-05-21 Thread James Shuriff
What do you think of updating the bare metals to 9.1.0? I don’t know anything outside of U-Boot and the PSCI Monitor (rpi-firmware) that actually depends on those ports and I've tested them with my custom ports. The powerpc64-gcc patches aren't needed to build the bare metal ports. Neither port

Re: maintenance of gcc cross ports

2019-05-21 Thread Mark Millard via freebsd-ports
On 2019-May-21, at 06:56, James Shuriff wrote: > What do you think of updating the bare metals to 9.1.0? I don’t know anything > outside of U-Boot and the PSCI Monitor (rpi-firmware) that actually depends > on those ports and I've tested them with my custom ports. The powerpc64-gcc > patches a

Re: maintenance of gcc cross ports

2019-05-21 Thread John Baldwin
On 5/21/19 6:56 AM, James Shuriff wrote: > What do you think of updating the bare metals to 9.1.0? I don’t know anything > outside of U-Boot and the PSCI Monitor (rpi-firmware) that actually depends > on those ports and I've tested them with my custom ports. The powerpc64-gcc > patches aren't ne

UNAME_r and OSVERSION mismatch - annoying error

2019-05-21 Thread Grzegorz Junka
Hi, poudriere options -c -j 12rel0 -p local -z desktop audio/sdl_sound throws at me: make: "/usr/local/poudriere/ports/gui/Mk/bsd.port.mk" line 1203: UNAME_r (12.0-RELEASE-p4) and OSVERSION (1102000) do not agree on major version number. What's the easiest way for (temporarily) disabling th

Re: FYI: Unable to build -r501994 ports' devel/qt5-core on clang 8 based powerpc64 system: "Q_ATOMIC_INT64_IS_SUPPORTED must be defined on a 64-bit platform"

2019-05-21 Thread Mark Millard via freebsd-ports
I'm top posting because the problem originally reported seems to be a later consequence of a much earlier problem. Looking in the logs showed lots of use of -I%%LOCALBASE%%/lib/gcc8/include/c++ and looking in: /wrkdirs/usr/ports/devel/qt5-core/work/qtbase-everywhere-src-5.12.2/mkspecs/freebsd-g++/

Re: FYI: Unable to build -r501994 ports' devel/qt5-core on clang 8 based powerpc64 system: "Q_ATOMIC_INT64_IS_SUPPORTED must be defined on a 64-bit platform"

2019-05-21 Thread Mark Millard via freebsd-ports
On 2019-May-21, at 16:20, Mark Millard wrote: > I'm top posting because the problem originally reported seems to be > a later consequence of a much earlier problem. Looking in the logs > showed lots of use of -I%%LOCALBASE%%/lib/gcc8/include/c++ and looking in: > > /wrkdirs/usr/ports/devel/qt

Re: graphics/php*-gd requires X11 by default

2019-05-21 Thread Greg Kennedy
Never mind! I just saw that this was fixed in October for php73-gd. Need to update my PHP version. On Thu, May 16, 2019 at 8:54 PM Greg Kennedy wrote: > I'm raising this again as the last time I tried to check with the port > maintainer, he had not made the change, and wasn't available to do s

Re: FYI: Unable to build -r501994 ports' devel/qt5-core on clang 8 based powerpc64 system: "Q_ATOMIC_INT64_IS_SUPPORTED must be defined on a 64-bit platform"

2019-05-21 Thread Mark Millard via freebsd-ports
[I've tested the proposed Mk/Uses/qt-dist.mk fix.] On 2019-May-21, at 17:15, Mark Millard wrote: > On 2019-May-21, at 16:20, Mark Millard wrote: > >> I'm top posting because the problem originally reported seems to be >> a later consequence of a much earlier problem. Looking in the logs >> sho