Re: GSOC Ideas

Dear Marcus, Thank you very much for the extensive list of fresh ideas :) Just a few general explanations. One general rule is that the suggested ideas should be something that a mentor is able to implement himself in cca. 3 weeks. There might be exceptions if you meet a really brilliant student

OSX 10.6 clang / llvm circular dependency

It looks like on OSX 10.6 (and, thus possibly elsewhere) that llvm-7.0 and clang-7.0 create a circular dependency ... see the attached info. Not sure how to work around this, but it is quite a PITA to do the equivalent of "sudo port upgrade outdated" manually port by port ... Hoping someone can

Currently recommended Python version?

I was about to update one of my ports, libcec, which currently depends on python34. I see that python37 was added to MacPorts in the middle of 2018. I don’t even know how libcec actually uses python. I can’t see anything documented for the package that specifies or recommends a particular ver

Re: Currently recommended Python version?

Hi Craig, > On Feb 8, 2019, at 9:17 AM, Craig Treleaven wrote: > > I was about to update one of my ports, libcec, which currently depends on > python34. I see that python37 was added to MacPorts in the middle of 2018. > I don’t even know how libcec actually uses python. I can’t see anythin

Re: OSX 10.6 clang / llvm circular dependency

Hi, Clearly clang-7.0 and llvm-.7.0 cannot depend on clang-7.0 as a build dependency, that will never work. I do not see this though myself, in my OSX10.6 VM. There they both depend on clang-3.7 to build. See below. This is fine. You must have done something locally in your checkout to caus

Re: OSX 10.6 clang / llvm circular dependency

I ran into a similar situation last week trying to do the clang-5.0 builds recommended under the smtube thread. Perhaps something similar is occurring here? On 2/8/19 11:40 AM, Chris Jones wrote: Hi, Clearly clang-7.0 and llvm-.7.0 cannot depend on clang-7.0 as a build dependency, that will

Re: OSX 10.6 clang / llvm circular dependency

I'm trying rebuilding the PortIndex ... but, otherwise no the port tree is at the current GIT master and clean. I'm investigating ... - MLD On Fri, Feb 8, 2019, at 11:40 AM, Chris Jones wrote: > Hi, > > Clearly clang-7.0 and llvm-.7.0 cannot depend on clang-7.0 as a build > dependency, that wil

Re: OSX 10.6 clang / llvm circular dependency

Hi, I was more referring to your macports configuration than the ports tree itself. Are you sure you aren’t overriding the compiler configuration from what would otherwise be the default setting ? That would be my best guess. Chris > On 8 Feb 2019, at 6:23 pm, Michael Dickens wrote: > > I'm

Re: OSX 10.6 clang / llvm circular dependency

Try updating and going again; 7.0 needed to be added to the blacklist-if-not-installed loop in libomp. Not sure if this is your issue, but can't hurt. On Fri, Feb 8, 2019 at 12:52 PM Chris Jones wrote: > Hi, > > I was more referring to your macports configuration than the ports tree > itself. A

Re: OSX 10.6 clang / llvm circular dependency

Updated; rebuilt the PortIndex. No different. I find the following very curious. "cmake" depends on itself circularly, which just can't be good; and, the internal cmake dependency has somewhat different dependencies compared with the outer one. It also has direct dependencies on clang- 7.0 and llvm

Re: OSX 10.6 clang / llvm circular dependency

> On 8 Feb 2019, at 7:43 pm, Michael Dickens wrote: > > Updated; rebuilt the PortIndex. No different. I find the following very > curious. "cmake" depends on itself circularly, which just can't be good; and, > the internal cmake dependency has somewhat different dependencies compared > with

Re: OSX 10.6 clang / llvm circular dependency

On Fri, Feb 8, 2019, at 3:02 PM, Christopher Jones wrote: >> On 8 Feb 2019, at 7:43 pm, Michael Dickens >> wrote:>> >> Updated; rebuilt the PortIndex. No different. I find the following >> very curious. "cmake" depends on itself circularly, which just can't >> be good; and, the internal cmake dep

Re: OSX 10.6 clang / llvm circular dependency

OK some more sleuthing turns up that the issue was not the cxx11 PG, but rather this line in the cmake Portfile:{{{ configure.cxx_stdlib libc++ }}} before this line, the compiler is 'gcc-4.2', while after it is 'macports-clang-7.0' ... I'll keep poking, but I'm about done with the rabbit hole ... -

Re: OSX 10.6 clang / llvm circular dependency

> On 8 Feb 2019, at 8:55 pm, Michael Dickens wrote: > > OK some more sleuthing turns up that the issue was not the cxx11 PG, but > rather this line in the cmake Portfile: > {{{ > configure.cxx_stdlib libc++ > }}} > before this line, the compiler is 'gcc-4.2', while after it is > 'macports-cla

Re: OSX 10.6 clang / llvm circular dependency

My ports tree is up to date with no modifications, according to "git". Note that the 'if' clause that this line is in is -not- of the arguments, so it is valid for OSX with uname major >= 10 -- which includes OSX 10.6 (== 10). On Fri, Feb 8, 2019, at 4:01 PM, Chris Jones wrote: > On 8 Feb 2019, at

Re: OSX 10.6 clang / llvm circular dependency

Adding in some debug printouts inside portconfigure.tcl, I think what's happening is that when "libc++" is specified, somewhere inside portconfigure.tcl the possible compilers to used gets pared down. Since I'm not specifying one by default, and there is no blacklist or whitelist, the fallback list

Re: OSX 10.6 clang / llvm circular dependency

> On 8 Feb 2019, at 9:32 pm, Michael Dickens wrote: > > Adding in some debug printouts inside portconfigure.tcl, I think what's > happening is that when "libc++" is specified, somewhere inside > portconfigure.tcl the possible compilers to used gets pared down. Since I'm > not specifying one

Re: OSX 10.6 clang / llvm circular dependency

On 2019-2-9 08:39 , Christopher Jones wrote: > > >> On 8 Feb 2019, at 9:32 pm, Michael Dickens > > wrote: >> >> Adding in some debug printouts inside portconfigure.tcl, I think >> what's happening is that when "libc++" is specified, somewhere >> inside portconfigure

Re: Load dynamic library for python library

> On Feb 7, 2019, at 8:05 PM, Joshua Root > wrote: > > On 2019-2-8 13:59 , Casey Deccio wrote: >> >> >>> On Feb 7, 2019, at 7:03 PM, Joshua Root >> > wrote: >>> >>> BTW Gmail decided my reply was spam; sending only to the list this time >>>

Re: Load dynamic library for python library

On 2019-2-9 09:20 , Casey Deccio wrote: > >> On Feb 7, 2019, at 8:05 PM, Joshua Root > > wrote: >> >> The call is in libnacl/__init__.py. I'd patch in a placeholder and use >> reinplace to insert the value of $prefix. > > Thanks!  So would it be better for the patch to t

Re: Load dynamic library for python library

> On Feb 8, 2019, at 4:05 PM, Joshua Root wrote: > > > I already committed the change. Whoops - I see that now. Thanks! > No fallback because we only want to use > the MacPorts version of libsodium. There's a dependency on it, so if > it's missing something has gone very wrong. Indeed. Th

Re: Load dynamic library for python library

> On Feb 8, 2019, at 4:05 PM, Joshua Root wrote: > > > I already committed the change. Whoops - I see that now. Thanks! > No fallback because we only want to use > the MacPorts version of libsodium. There's a dependency on it, so if > it's missing something has gone very wrong. Indeed. Th

Re: OSX 10.6 clang / llvm circular dependency

> On 8 Feb 2019, at 10:19 pm, Joshua Root wrote: > >> On 2019-2-9 08:39 , Christopher Jones wrote: >> >> >>> On 8 Feb 2019, at 9:32 pm, Michael Dickens >> > wrote: >>> >>> Adding in some debug printouts inside portconfigure.tcl, I think >>> what's happening is