Re: [macports-ports] branch master updated: net/wireshark2: update to 2.2.7 resolves #54272

2017-06-02 Thread Rainer Müller
On 06/03/2017 01:15 AM, Ryan Schmidt wrote: > (I don't think we're recognizing the word "resolves" as a synonym of > "closes".) We are using the defaults of Trac's CommitTicketUpdater: Close ticket: close closed closes fix fixed fixes Reference ticket: addresses re references refs see htt

Re: [macports-ports] branch master updated: net/wireshark2: update to 2.2.7 resolves #54272

2017-06-02 Thread Ryan Schmidt
> On Jun 2, 2017, at 14:20, Eric Hall wrote: > > ghosthound pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/85120c45eab3efca80ee8d296f71cac579d99fad > > The following commit(s) were added to refs/heads/master by this pus

Re: about the libc++ conversion

2017-06-02 Thread Ken Cunningham
> However, if I read what's said about this on Linux forums I get the > impression > that the linker should or might raise errors because of the use of different > namespaces. That's right. I've seen errors that look like this, with this std::__1 business: Undefined symbols for architecture x

Re: about the libc++ conversion

2017-06-02 Thread rjvbertin
Chris Jones wrote: > So all you have proved is, in your examples, you do not trip over this. > You have not proved in gerenal it is a safe thing to do. Not claiming to either, and I have tried Qt code above all. While usually highly complex I don't think it uses many STL or std classes. Howe

Re: about the libc++ conversion

2017-06-02 Thread Ken Cunningham
> simplify the libc++ conversion on older OS X versions I'm working on something related. It turns out that Clang-3.8 / llvm 3.8 builds without too much trouble on 10.5 PPC, using gcc6 to build it (see my trac tickets if you would like to see how to do that). It can then build quite complex

Re: about the libc++ conversion

2017-06-02 Thread Chris Jones
Hi, The fact that in some cases mixing the two C++ runtimes does not lead to obvious issues is *not* a general proof that there is not a problem in doing this. The issues generally occur when the application passing information between the two runtimes, if in those two runtimes the same type

about the libc++ conversion

2017-06-02 Thread René J . V . Bertin
Hi, This is mostly out of curiosity and for personal education. I've been tinkering a bit with the libcxx port, upgrading it to 4.0.0 and getting it to build on Linux to have a reproducable way of installing libc++ there. I went with the standard build that uses libstdc++ instead of libc++abi