On Nov 2, 2017, at 14:34, Ken Cunningham wrote:
> On Nov 2, 2017, at 12:20 PM, Ryan Schmidt wrote:
>
>> The part where it allows a port to be compiled with MacPorts libstdc++. Why
>> is this ok? Didn't we used to have the problem that C++ software compiled
>> with gcc would crash because it us
> On Nov 2, 2017, at 12:20 PM, Ryan Schmidt wrote:
> The part where it allows a port to be compiled with MacPorts libstdc++. Why
> is this ok? Didn't we used to have the problem that C++ software compiled
> with gcc would crash because it used new gcc libstdc++ but a library it used
> was us
On Nov 2, 2017, at 14:08, Joshua Root wrote:
> On 2017-11-3 05:39 , Ryan Schmidt wrote:
>>
>> On Nov 2, 2017, at 13:00, Joshua Root wrote:
>>
>>> The reason for the ABI incompatibilities is, AIUI, that before C++11 the
>>> C++ standard did not specify an ABI. So theoretically mixing libc++ and
On 2017-11-3 05:39 , Ryan Schmidt wrote:
>
> On Nov 2, 2017, at 13:00, Joshua Root wrote:
>
>> The reason for the ABI incompatibilities is, AIUI, that before C++11 the
>> C++ standard did not specify an ABI. So theoretically mixing libc++ and
>> libstdc++ works just as well whether you are on Lin
On Thu, Nov 2, 2017 at 7:39 AM, Mojca Miklavec wrote:
> I would have appreciated if Marcus would at least mention it before
> committing the new subport, I was just as confused when I saw it two
> days ago as you are.
At the time, I felt the change fell under the openmaintainer policy.
My apologi
On Nov 2, 2017, at 13:00, Joshua Root wrote:
> The reason for the ABI incompatibilities is, AIUI, that before C++11 the
> C++ standard did not specify an ABI. So theoretically mixing libc++ and
> libstdc++ works just as well whether you are on Linux or macOS -- that
> is to say, if everything is
>> Begin forwarded message:
>>
>> From: Vadim Zeitlin
>> As an aside, under Linux it's actually possible to mix and match
>> -std=c++xx options when building the library and the applications, but this
>> is due to gcc/libstdc++ carefully maintaining the ABI and I'm all but sure
>> that this is not
On 2017-11-3 00:28 , Ryan Schmidt wrote:
> Well, but still, should we remove pypi.python.org from the pypi fetchgroup,
> or are there some ports for which it still works where files.pythonhosted.org
> wouldn't work?
Yeah, it's there for releases from before the files.pythonhosted.org
redirector
Forwarding reply from Vadim who is not subscribed.
> Begin forwarded message:
>
> From: Vadim Zeitlin
> Subject: Re[2]: Question about compiler blacklisting (llvm-gcc for wxWidgets)
> Date: November 2, 2017 at 09:25:24 CDT
> To: Ryan Schmidt, Mojca Miklavec
> Cc: Ken Cunningham, MacPorts Develope
On 2 November 2017 at 15:16, Ryan Schmidt wrote:
>
> So wait... does wxWidgets require C++11 or not? If it does, that settles the
> discussion; treat it like any other port that requires C++11 and include the
> cxx11-1.1 portgroup.
No, it doesn't. But one needs a C++11 flavour of it if another p
On Nov 2, 2017, at 06:39, Mojca Miklavec wrote:
> But generally the problems fall into some very similar category as
> mix-and-matching C++11 and pre-C++11 compilers. The wxWidgets does all
> kinds of build-time testing for various features and then remembers
> the results in some equivalent of c
On Nov 1, 2017, at 19:09, Toby Peterson wrote:
> tobypeterson pushed a commit to branch master
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/20d860625d3d6087809bfff4c578f70edf01a527
>
> The following commit(s) were added to refs/heads/master by this pu
On Nov 2, 2017, at 06:36, Russell Jones wrote:
> On 02/11/17 11:06, Ryan Schmidt wrote:
>
>> On Nov 2, 2017, at 05:49, Russell Jones wrote:
>>
>>> I'm working on a few python ports using the Python 1.0 PortGroup, and I get
>>> 404s for the download link. e.g. for Python module xyz version 1.2.3
On 2 November 2017 at 12:01, Ryan Schmidt wrote:
> On Nov 1, 2017, at 11:29, Mojca Miklavec wrote:
>
>> I'm currently trying to fix wxWidgets-3.0 in various ways. One of the
>> problems of the latest release is that it compiles fine with both
>> clang >= 500 and llvm-gcc. If I blacklist clang < 500
Right. I had a feeling I was missing something.
Ah, hold on. The extension's changed to .zip from .tar.gz, that's the
problem. Sorry for the noise.
Russell
On 02/11/17 11:06, Ryan Schmidt wrote:
On Nov 2, 2017, at 05:49, Russell Jones wrote:
I'm working on a few python ports using the Pyt
On Nov 2, 2017, at 05:49, Russell Jones wrote:
> I'm working on a few python ports using the Python 1.0 PortGroup, and I get
> 404s for the download link. e.g. for Python module xyz version 1.2.3, it
> looks for https://pypi.python.org/packages/source/x/xyz/xyz-1.2.3.tar.gz
> Trying this for a
On Nov 1, 2017, at 11:29, Mojca Miklavec wrote:
> I'm currently trying to fix wxWidgets-3.0 in various ways. One of the
> problems of the latest release is that it compiles fine with both
> clang >= 500 and llvm-gcc. If I blacklist clang < 500 on Lion, it will
> fallback to llvm-gcc which works i
Hello All,
I'm working on a few python ports using the Python 1.0 PortGroup, and I
get 404s for the download link. e.g. for Python module xyz version
1.2.3, it looks for
https://pypi.python.org/packages/source/x/xyz/xyz-1.2.3.tar.gz Trying
this for a few random modules, it always comes back 4
18 matches
Mail list logo
