[MacPorts] #41316: qt4-mac: Warning about libstdc++ after installation ( r113176 does not work for me )

[MacPorts]

#41316: qt4-mac: Warning about libstdc++ after installation ( r113176 does not work
for me )
-----------------------------------+--------------------------------
  Reporter:  george.sklivanitis@…  |      Owner:  macports-tickets@…
      Type:  defect                |     Status:  new
  Priority:  Normal                |  Milestone:
 Component:  ports                 |    Version:  2.2.1
Resolution:                        |   Keywords:  mavericks
      Port:  qt4-mac               |
-----------------------------------+--------------------------------

Old description:

> I have the qt4-mac port installed on Mavericks. However, I always see the
> following warning after building ports:
>
> sudo port install gnuradio +all
> --->  Computing dependencies for gnuradio
> --->  Cleaning gnuradio
> --->  Scanning binaries for linking errors: 81.4%
> Warning: /opt/local/bin/qmake uses /usr/lib/libstdc++.6.dylib as C++
> standard library although macports::cxx_stdlib is set to libc++.
> --->  Scanning binaries for linking errors: 100.0%
> --->  No broken files found.
>

> I followed the instructions of r113176 but still I have the same problem

New description:

 I have the qt4-mac port installed on Mavericks. However, I always see the
 following warning after building ports:

 {{{
 sudo port install gnuradio +all
 --->  Computing dependencies for gnuradio
 --->  Cleaning gnuradio
 --->  Scanning binaries for linking errors: 81.4%
 Warning: /opt/local/bin/qmake uses /usr/lib/libstdc++.6.dylib as C++
 standard library although macports::cxx_stdlib is set to libc++.
 --->  Scanning binaries for linking errors: 100.0%
 --->  No broken files found.
 }}}

 I followed the instructions of r113176 but still I have the same problem

--

Comment (by cal@…):

 This is a false positive, IMO. I'm not very happy with this warning, since
 it's essentially in the wrong place. This shouldn't be printed every time
 rev-upgrade runs, but in a new to-be-written phase after destroot. Porting
 to libc++ is not a no-brainer, especially for larger projects, and should
 probably be left for upstream.

-- 
Ticket URL: <https://trac.macports.org/ticket/41316#comment:1>
MacPorts <http://www.macports.org/>
Ports system for OS X