On 20 March 2018 at 16:56, Perry E. Metzger wrote:
> On Mon, 19 Mar 2018 21:46:54 -0500 Ryan Schmidt wrote:
>>
>> I would prefer that the bug that protobuf-cpp and protobuf3-cpp
>> install to the same place is fixed first:
>>
>> https://trac.macports.org/ticket/56102
>>
>> Then there's no reason wh
On Tue, 20 Mar 2018 11:59:01 -0400 "Perry E. Metzger"
wrote:
> On Mon, 19 Mar 2018 11:44:48 -0400 "Perry E. Metzger"
> wrote:
> >
> > 1: wine*: add 64-bit support
> >https://github.com/macports/macports-ports/pull/442
> >Apr 22, 2017 (yes, almost a year old)
>
> There seems to be a con
On Mon, 19 Mar 2018 11:44:48 -0400 "Perry E. Metzger"
wrote:
>
> 1: wine*: add 64-bit support
>https://github.com/macports/macports-ports/pull/442
>Apr 22, 2017 (yes, almost a year old)
There seems to be a consensus that the 64 bit stuff _should_ be
committed for the sake of those apps th
On Mon, 19 Mar 2018 21:46:54 -0500 Ryan Schmidt
wrote:
> > 2: mosh: Switch to protobuf3-cpp
> > https://github.com/macports/macports-ports/pull/690
> > Aug 17, 2017
> >
> > Zero King correctly notes in the course of the PR's comment thread
> > that protobuf3-cpp conflicts with protobuf-cpp, s
On Mar 19, 2018, at 10:44, Perry E. Metzger wrote:
> There are a few pull requests that are pretty old and which I think
> are, de facto, stuck. I'd like to get some feedback about what to do
> about them.
>
> If we can close these three, we will have no PRs older than six months
> active in the
On 2018-3-20 05:14 , Leonardo Brondani Schenkel wrote:
> On 2018-03-19 18:17, Ken Cunningham wrote:
>>> There's no good way to shim the ABI without having something
>>> physically deal with this problem, which likely requires a lot of
>>> work on very low level hacking.
>>
>> When last I read about
On 2018-03-19, at 10:03 AM, Perry E. Metzger wrote:
> So my understanding (and I might be mangling it) is that the issue
> here is that there are two x86_64 registers that are reasonable
> candidates for pointing at thread local data, and Windows has picked
> a different one from macOS. The resu
On Mon, 19 Mar 2018 14:27:44 -0400 "Perry E. Metzger"
wrote:
> On Mon, 19 Mar 2018 11:17:21 -0600 Ken Cunningham
> wrote:
> > >
> > > There's no good way to shim the ABI without having something
> > > physically deal with this problem, which likely requires a lot
> > > of work on very low level
On Mon, 19 Mar 2018 19:29:35 +0100 Rainer Müller
wrote:
[On the Wine 64 bit issue]
> > So my understanding (and I might be mangling it) is that the issue
> > here is that there are two x86_64 registers that are reasonable
> > candidates for pointing at thread local data, and Windows has
> > pi
On 19 March 2018 at 19:29, Rainer Müller wrote:
>
> Unfortunately, we have no support to run builds from pull requests or
> custom branches on the buildbot, as it would immediately publish the
> resulting archives.
>
> This sounds like a nice enhancement for our buildbot, though. On a
> forced buil
On 2018-03-19 18:03, Perry E. Metzger wrote:
> On Mon, 19 Mar 2018 17:10:52 +0100 Mojca Miklavec
>> Last time I checked this PR was not entirely complete and from my
>> understanding that was the only reason why it was not merged. We
>> certainly need a solution for 64-bit wine in some not-too-dist
On Mon, 19 Mar 2018 11:17:21 -0600 Ken Cunningham
wrote:
> >
> > There's no good way to shim the ABI without having something
> > physically deal with this problem, which likely requires a lot of
> > work on very low level hacking.
>
> When last I read about this, the Wine devs were asking for
On 2018-03-19 18:17, Ken Cunningham wrote:
There's no good way to shim the ABI without having something
physically deal with this problem, which likely requires a lot of
work on very low level hacking.
When last I read about this, the Wine devs were asking for compiler support in
clang to acco
>
> There's no good way to shim the ABI without having something
> physically deal with this problem, which likely requires a lot of
> work on very low level hacking.
When last I read about this, the Wine devs were asking for compiler support in
clang to accomplish this feat.
I bet they will g
On Mon, 19 Mar 2018 17:10:52 +0100 Mojca Miklavec
wrote:
> On 19 March 2018 at 16:44, Perry E. Metzger wrote:
> >
> > 1: wine*: add 64-bit support
> >https://github.com/macports/macports-ports/pull/442
> >Apr 22, 2017 (yes, almost a year old)
> >
> > This PR seems to be stuck on the fact t
On 19 March 2018 at 16:44, Perry E. Metzger wrote:
>
> 1: wine*: add 64-bit support
>https://github.com/macports/macports-ports/pull/442
>Apr 22, 2017 (yes, almost a year old)
>
> This PR seems to be stuck on the fact that Wine de facto needs a 64
> bit version to be useful in a modern cont
There are a few pull requests that are pretty old and which I think
are, de facto, stuck. I'd like to get some feedback about what to do
about them.
If we can close these three, we will have no PRs older than six months
active in the system, which I think is a win.
1: wine*: add 64-bit support
17 matches
Mail list logo
