Re: Problems cross-compiling with clang 3.7 & 3.9 on 10.6

On 28 March 2017 at 17:37, Ken Cunningham wrote: > On 2017-03-28, at 2:18 AM, Mojca Miklavec wrote: > > It had always been a design goal for llvm to produce workable PPC code, but > although close (lots of things do work) they never quite got there (Jeremy > has most of the bugs outlined on the llv

Re: [macports-ports] 01/02: pkcs11-helper: update to 1.22, depend on pkg-config to fix trace-mode build

> On Feb 18, 2017, at 14:49, Dan Villiom Podlaski Christiansen > wrote: > > Dan Villiom Podlaski Christiansen (danchr) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/7e1fe0ddffb75d7262e3e3edeed03ab18d284049 > > commit

Re: GSoC'17: Add migrate action to port command Project

Hi > I believe at a minimum we should plan on two new actions, port “snapshot” > and “migrate”. A snapshot will the installed ports, their variants and if > the port was “requested”. > > The migrate action will call the snapshot action to create and/or use > snapshots to rebuild ports on the new

Re: citing git commits on Trac?

> On Mar 28, 2017, at 09:23, Rainer Müller wrote: > > On 2017-03-28 15:34, Joshua Root wrote: >> Documentation is available at . >> >> I find the easiest way to link to a commit is [committish/repo], e.g. >> [42a4d67a/macports-ports]. Apparently you nee

Re: GSoC'17: Add migrate action to port command Project

> On Mar 28, 2017, at 11:55 AM, Umesh Singla wrote: > > Hi Brad, > > I'm UTC +5:30. Around 10:00 to 15:00 (UTC -8) is a good time, I suppose. Ok, good, you make it easy for me :) > I have been going through discussion on the mailing list again and found that > the automating the tasks given

Re: GSoC'17: Add migrate action to port command Project

Hi Brad, I'm UTC +5:30. Around 10:00 to 15:00 (UTC -8) is a good time, I suppose. I have been going through discussion on the mailing list again and found that the automating the tasks given under Migration documentation is just a start for the port migration tool we need. Can you tell me what ot

Re: GSoC'17: Add migrate action to port command Project

> On Mar 23, 2017, at 9:08 PM, Jackson Isaac wrote: > > Hi Umesh, > > > First of all, Welcome to The MacPorts Project. We are always happy to > see new developers around. Yes, welcome. > On Fri, Mar 24, 2017 at 4:30 AM, Umesh Singla wrote: >> Hello, >> >> As we discussed on IRC, I've been l

Re: Problems cross-compiling with clang 3.7 & 3.9 on 10.6

On 2017-03-28, at 2:18 AM, Mojca Miklavec wrote: > > It makes absolutely no sense that I try to use a compiler that has > never been designed or tested to produce binaries for PPC. It had always been a design goal for llvm to produce workable PPC code, but although close (lots of things do work

Re: citing git commits on Trac?

On 2017-03-28 15:34, Joshua Root wrote: > Documentation is available at . > > I find the easiest way to link to a commit is [committish/repo], e.g. > [42a4d67a/macports-ports]. Apparently you need at least 8 characters of > the hash, which is slightly anno

Re: citing git commits on Trac?

On 2017-3-29 00:09 , Peter Danecek wrote: Hi all, do we have some convention on how to cite git commits on Trac? I see that the "Commit Ticket Updater" uses the following format / and links to an URL on Trac, which then is redirected to GitHub. Are we supposed to do the same manually when citin

citing git commits on Trac?

Hi all, do we have some convention on how to cite git commits on Trac? I see that the "Commit Ticket Updater" uses the following format / and links to an URL on Trac, which then is redirected to GitHub. Are we supposed to do the same manually when citing commits? Is there some support for this

Re: Problems cross-compiling with clang 3.7 & 3.9 on 10.6

On 28 March 2017 at 05:07, Ken Cunningham wrote: > It's been a few months since I went down this rabbit hole, but IIRC, > it worked a little better to build clang on ppc directly. Just to clarify. I want to compile some software for multiple architecture and provide backwards compatibility for as