On 9/4/15 6:17 PM, Ryan Schmidt wrote:
> 
> On Sep 4, 2015, at 12:56 AM, FritzS wrote:
> 
>> I hope you could resolve the problem with the pan2 installation
> 
> It is not our problem to resolve. The developers of pan2 need to make their 
> code compatible with libc++. But they have not responded to the bug report I 
> filed about this in 2013:
> 
> https://bugzilla.gnome.org/show_bug.cgi?id=712539
> 
>> the current sources from pan are older - 29-Jun-2012 22:31
>>
>> http://pan.rebelbase.com/download/releases/0.139/source/
>> or
>> https://git.gnome.org/browse/pan2/
>>
>> The general problem, many developer had stopped the develop of usenet reader 
>> too, unfortunately usenet is going down.
> 
> 
> It looks like development of pan2 has not necessarily stopped, since there 
> are commits to the repository as recently as 4 months ago:
> 
> https://git.gnome.org/browse/pan2/log/
> 
> However, even the latest code in the repository still fails to build with 
> libc++ with the same error.
> 
> If you want the problem resolved, either you need to fix their code to work 
> with libc++, or you need to convince the developers of pan2 to do so.
> 
> 

Ryan --

I can confirm that the current git master (version 0.140, gtk2 build, dated 
2015-05-15, not yet released) fails to build
on Yosemite using the default libc++.  However, it does build and run with 
libstdc++ using

configure.cxx_stdlib libstdc++

because none of its dependencies use libc++.

Since it's not likely that any other port using libc++ will have a binary 
dependency on pan2, isn't this a permissible
configuration for this port on Mavericks and Yosemite until the libc++ issue is 
addressed upstream? Haven't checked
whether this will work on El Capitan as yet.

Dave


_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Reply via email to