[MacPorts] #59980: qBittorrent: build failure on 10.11; silent rules prevent analysis

[MacPorts]

#59980: qBittorrent: build failure on 10.11; silent rules prevent analysis
------------------------+-------------------------
 Reporter:  ryandesign  |      Owner:  i0ntempest
     Type:  defect      |     Status:  assigned
 Priority:  Normal      |  Milestone:
Component:  ports       |    Version:  2.6.2
 Keywords:              |       Port:  qBittorrent
------------------------+-------------------------
 I'm not sure how many OS versions back qBittorrent wants to support, but I
 see
 [https://build.macports.org/builders/ports-10.11_x86_64-builder/builds/106143/steps
 /install-port/logs/stdio a build failure on 10.11]. The error is:

 {{{
 base/bittorrent/peeraddress.cpp:58:12: error: no matching constructor for
 initialization of 'BitTorrent::PeerAddress'
     return {ip, port};
            ^~~~~~~~~~
 base/bittorrent/peeraddress.h:37:12: note: candidate constructor (the
 implicit copy constructor) not viable: requires 1 argument, but 2 were
 provided
     struct PeerAddress
            ^
 base/bittorrent/peeraddress.h:37:12: note: candidate constructor (the
 implicit move constructor) not viable: requires 1 argument, but 2 were
 provided
 base/bittorrent/peeraddress.h:37:12: note: candidate constructor (the
 implicit default constructor) not viable: requires 0 arguments, but 2 were
 provided
 1 error generated.
 }}}

 I wonder if this is related to this prior warning:

 {{{
 ./base/tristatebool.h:43:9: warning: use of this statement in a constexpr
 constructor is a C++14 extension [-Wc++14-extensions]
         *this = boolean ? True : False;
         ^
 }}}

 The port does specify that it requires C++14, but perhaps the build system
 is not respecting our compiler choice. It's impossible to tell because the
 build log does not show the actual commands that were run to compile
 things: the build has some sort of "silent rules" enabled. Is there a way
 to disable silent rules? Then we can more easily debug further.

 If silent rules are a standard Qt feature—if this is a generic problem
 that affects other ports using the qt5 portgroup—then maybe a fix can go
 in the qt5 portgroup (just as we have such a fix already in the cmake
 portgroup).

-- 
Ticket URL: <https://trac.macports.org/ticket/59980>
MacPorts <https://www.macports.org/>
Ports system for macOS