Re: Removal of llvm-3.5 and llvm-3.6

roken ghc. > > On Sun, Jan 29, 2017 at 2:57 PM, Brandon Allbery <allber...@gmail.com> > wrote: > >> >> On Sun, Jan 29, 2017 at 2:51 PM, Ken Cunningham < >> ken.cunningham.web...@gmail.com> wrote: >> >>> > GHC still uses 3.5. I want to change that,

anyone in a mood to reject this hedgewars submission?

I’ve been trying to make macports more relevant to average users by bringing all the top ‘net games in. Some of them are a bit messy. Hedgewars is one of the top 10. It could have a better build script. It’s a game, though. The mods I made make it work correctly on Snow Leopard through Sierra,

Re: Handling C++11

Well, the entire c++ library on the buildbot would have to be rebuilt against libgcc's libstdc++ for this to work -- all of octave's deps and deps of deps would need to be built the same as octave, of course, and so everything else too. The whole machine has to be configured the same way (which is

Re: Handling C++11

Octave builds and runs great on older systems right now when they are upgraded to libc++ per the current instructions. $ port -v installed octave The following ports are currently installed: octave @4.2.0_1+accelerate+app+docs+fltk+gfortran+graphicsmagick+qt4+sound platform='darwin 10'

port requires c++1y -> use cxx11 portgroup?

The pingus port I put up last night (and which Ryan so kindly fixed while I was sleeping for a missing dependency and an error on case-sensitive file systems - gotta love those buildbots for finding these things - and thanks for that) requires the c++1y standard to build. Builds will fail on

Re: port requires c++1y -> use cxx11 portgroup?

> > > The main thing you get is that, without that portgroup, it will attempt to > build on older OS X and fail. It also supports the > https://trac.macports.org/wiki/LibcxxOnOlderSystems > workflow for those > users who have done it to

Re: ports using scons build system

> It seems to me that with scons, it's up to each project to write their build > system however they want, so there isn't much standardization with regard to > how the compiler and flags are specified. > OK. Thanks, everyone. - Ken

ports using scons build system

Would anyone like to point me towards a port that uses the scons build system properly in Macports? I have an idea how to go about importing all the build environment variables, but I don’t want to go to all the trouble only to find out there is a proper, sanctioned method that I’ll then have

Re: installing an older version of a port in the github era -- an answer

So, this turns out to be a lot easier than I originally thought it would be, and probably is no more difficult than svn was. This may not be the most efficient way of doing it, but it's fairly easy to understand, and it works for me. Here are (perhaps too many) steps regarding how to do it.

review request - glbinding - new C++ bindings for OpenGL

glbinding is a c++ binding for OpenGL that some OpenGL ports, eg widelands, are using for debugging at present and moving towards for general use. this is the current version as of today. appears to work without issues. All examples build and work correctly. would be needed for the devel+debug

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

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

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. 10.5 intel fails to build PPC correctly due to the runtime library issues you stumbled across. The highest i have been able to go is clang-3.6 on ppc so far (building it

Re: GSoC Proposal

Have you seen how homebrew does this? I imagine he means something like that: Every submission has to be submitted to the 10.10 - 10.12 bots first, to see if it builds. Every submission is suggested / required to have at least a minimal test `myport --version` to make sure something actually

Re: [macports-ports] branch master updated: mosh: 1.3.0, switch to CommonCrypto

so this sorta gets back to your question about support for older systems, and is a pretty typical example of same. sounds like you could write up an openssl variant for it, default to that variant on suitable systems, and nobody would likely complain about that. But you might have to do it and

Re: Tiger Virtual Machine on VirtualBox

. K > On Apr 22, 2017, at 5:34 PM, Ken Cunningham <ken.cunningham.web...@gmail.com> > wrote: > > I know some of you are interested in such things, at times… debugging > MacPorts, trying out a port, etc. > > A Tiger VM more or less works, with a few touchy parts tha

Tiger Virtual Machine on VirtualBox

I know some of you are interested in such things, at times… debugging MacPorts, trying out a port, etc. A Tiger VM more or less works, with a few touchy parts that may or may not improve over time, on the current version of VirtualBox.

configure.compiler=macports-clang-devel doesn't work. Is there a proper value?

Doesn’t seem to be an entry for clang-devel in > and some trial and error didn’t find it easily… Also, can’t spot an entry in

Re: Possible patch for sox build failure on 10.7

> Thank you Josh. I missed ./configure --disable-silent-libtool. I am a bit confused about this. According to >,

should cxx11 1.1 PortGroup also blacklist older clangs (< 600, say) during libc++ builds?

The libstdc++ section of this portgroup forces clang 4.0, and the PPC section forces gcc6. Those cover almost all current port compiler requirements. But there is still a hole in the libc++ section, and it happens often enough that older clangs (< 600 or so) have to be blacklisted on older

Re: should cxx11 1.1 PortGroup also blacklist older clangs (< 600, say) during libc++ builds?

I’m sorry - retract this. I see there is already a section where this is done that I had glossed past before. I’ll have to look into why I still need to fiddle with this sometimes. Sorry for noise. Ken > On Aug 12, 2017, at 3:02 PM, Ken Cunningham <ken.cunningham.web...@gmail.com>

running clang compiler test suite from within macports infrastructure?

I suspect only Jeremy or LarryV could answer this, but is it possible to run the llvm / clang compiler test suite from within the macports infrastructure? The clang build on macports is very heavily modified with patches and configuration settings - it seems overwhelming to try to duplicate

Re: Is it time for a libc_fixes library yet?

p.c.auto.html > > https://opensource.apple.com/source/Libc/Libc-1158.50.2/string/FreeBSD/strnlen.c.auto.html > > > > > On Mon, Jul 3, 2017 at 3:26 PM, Ken Cunningham > <ken.cunningham.web...@gmail.com> wrote: > I see a general frustration with the current situation

Re: Is it time for a libc_fixes library yet?

> > > Perfect would be if I just wrote it into the clang code directly. I am almost > to the point where I could do that, actually. I know where it would go, I > think. > Well, another fairly easy option would be to bring down the newer libc from 10.7 and port it back into 10.4 to 10.6,

Re: Is it time for a libc_fixes library yet?

, Rainer Müller wrote: > On 2017-07-03 19:07, Ken Cunningham wrote: >> So the last 10 or so tickets in trac seem like they are all for >> basically the same issue - a few missing symbols from libc prior to 10.7. > > Well, I would take this as a reason to just drop support for suc

Is it time for a libc_fixes library yet?

So the last 10 or so tickets in trac seem like they are all for basically the same issue - a few missing symbols from libc prior to 10.7. It is easy enough, but time consuming, to patch each individual source file that is missing the definition (there might be several, also, so you might have

Re: Buildbot now fails to build wine dependencies

On 2017-06-27, at 2:31 AM, Ryan Schmidt wrote: > We used to be able to build wine on the buildbot, but we aren't anymore: > > https://build.macports.org/builders/ports-10.12_x86_64-builder/builds/32791 > > The error occurs when installing dependencies, specifically cairo: This would also be

Re: [macports-ports] branch master updated: cxx11 1.1 PortGroup: add support for PowerPC

Sorry 'bout that. https://github.com/macports/macports-ports/pull/563 On 2017-07-05, at 1:06 PM, Rainer Müller wrote: >> _resources/port1.0/group/cxx11-1.1.tcl

Re: Possible patch for sox build failure on 10.7

I'm travelling with a 10.7 laptop this summer (hence the rash of 10.7 fixes I've sent up over the past month). Can give it a try. --K > On Aug 9, 2017, at 1:05 AM, Joshua Root wrote: > > Perhaps someone with access to a 10.7 machine could try this. > > - Josh >

looking for a little help and feedback for irrlicht port (to enable minetest)

In my ongoing quest to bring every major open-source game to MacPorts, I've been working on minetest. Minetest is reported to be the #1 most popular open-source game on the internet. It's been in homebrew for a long time, but was broken there. I fixed it about six months back for homebrew, but

Re: looking for a little help and feedback for irrlicht port (to enable minetest)

Thanks for looking, Craig. I think you may have stumbled across this error. Ken >> My build file and patches are here: >> >> >> The minetest portfile and

some PRs for new and updated games ready to commit when you have a moment

Hello, all -- I believe the following additions and upgrades to macports games collection are in supportable condition, and IMHO are all ready to join the main Macports repository when/if you have a moment. -- Thanks, Ken scummvm: update 1.90, add devel version all Travis test build

Re: Tiger Virtual Machine on VirtualBox

it on 10.4 has borne fruit. See this thread for more if interested: <https://lists.cairographics.org/archives/cairo/2017-January/027836.html> Ken On 2017-05-02, at 12:28 PM, Joshua Root wrote: > On 2017-4-23 10:34 , Ken Cunningham wrote: >> I know some of you are interested in such t

Re: c++ library usage

>> >> - it was slightly easier to switch the system compiler/stdlib (in >> particur switching to the latest gcc on 10.5 for example) That particular piece is fairly easy. Just put this in macports.conf: default_compilers macports-gcc-6 and you're done. Every port will compile with gcc6,

Re: about the libc++ conversion

> 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

> 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

clang-3.8 on 10.4 and 10.5 PPC - available for testing for the adventuresome

I believe I have clang-3.8 / llvm-3.8 to a state now where people with these machines who are, shall we say, advanced MacPorters might want to waste a few minutes (and four hours building) to try it. If setting up a repo and figuring out your own dependencies is not peanuts for you, I wouldn't

Re: Installing WINE

Did this Very Big Problem with Wine64 on MacOS actually get fixed? K https://www.winehq.org/pipermail/wine-devel/2014-February/103074.html > I don’t know the exact details myself (Ken is the expert), but the answer is > that it does not work, and probably never will. OSX has a ABI

Re: application scope of configure.optflags, configure.compiler

> Is there any existing way I can get the configure.optflags or > configure.compiler command line argument to apply to multiple ports? for configure.compiler, setting default_compilers macports-clang-3.9 or whatever one you want seems to do the equivalent of setting configure.compiler

how to install a subport rather than the main port from a local Portfile not in a repository

Long title … If you download a Portile into a folder, you can quickly install or work with it with “sudo port -v install”, You don’t specify the name, and the primary port in the local Portfile is used. Is there a way to work with a subport contained in that Portfile in a similar fashion?

Re: how to install a subport rather than the main port from a local Portfile not in a repository

Thanks! Sorry to ask a previously-answered question… Ken > On Jun 11, 2017, at 7:36 AM, Daniel J. Luke <dl...@geeklair.net> wrote: > > On Jun 11, 2017, at 10:27 AM, Ken Cunningham > <ken.cunningham.web...@gmail.com> wrote: >> Is there a way to work with a subp

Re: Some opinions on whether there be a guile20 port?

> > geda-gaf > The other broken port(s) can no doubt be patched too. > > Actually, it looks like upgrading geda-gaf to use guile 2.2.2 may not be so easy after all. It may be stuck using guile 2.0.14 for some while. K

Re: travis builds time out -- then keep restarting ???

this is still going on. some travis builds have been running almost 6 hours, which would be great if they finally built something, but looks like it just keeps resetting and starting over... > On Sep 15, 2017, at 3:37 PM, Ken Cunningham <ken.cunningham.web...@gmail.com> > wrote: &g

Re: ignore "portfile changed" ?

thank you I don't think to check the man pages enough for macports issues. I will go look there more often. -- Ken > On Sep 17, 2017, at 7:41 AM, Rainer Müller <rai...@macports.org> wrote: > >> On 2017-09-17 16:35, Ken Cunningham wrote: >> when working on the dest

ignore "portfile changed" ?

when working on the destrooting of complex ports it is tedious to have the ports rebuild with each portfile edit, esp the big ports that need the complex destrooting It must be possible to override this -- I feel I'm missing something simple somewhere. I hope this detail is not just buried

Re: how to efficiently work through generating patches using git and macports build process?

Just like to say that this method works extremely well. Thanks! Ken On 2017-08-30, at 11:19 AM, Michael Dickens wrote: > You can always create or add them to a .gitignore file. If at the top-level > GIT repo, this file impacts the whole repo. You would literally add "*.o" > (but without

Re: Some opinions on whether there be a guile20 port?

Ah, the old version is 2.0.14, not 2.0.18, apologies for the typo. K On 2017-09-13, at 10:22 PM, Ken Cunningham wrote: > guile moved to 2.2.2 a few months ago, and at least two ports that link > against guile 2.0.18 broke when 2.2 rolled out: > > geda-gaf <https://trac.macp

travis builds time out -- then keep restarting ???

Something funny is going on with travis today. The builds keep restarting after timing out at 48 mins, I think

Re: [macports-ports] branch master updated: fish: fix build on Tiger

Thanks, will do. I was originally going to range it — then realized I was already at the bottom of the OS pile, and darwin 8 was as low as we can go :> It gives me such odd satisfaction to keep these old machines in current software … reduce, reuse, recycle, all that. Ken > On Oct 7, 2017,

virtual machine for 10.5 intel ?

if anyone would care to enlighten me on the best approach to making a VM for 10.5 intel, I would appreciate it. This is the only system I have that I can’t presently see a way to virtualize. Thanks, Ken

Re: virtual machine for 10.5 intel ?

Thanks for the ideas, Ken On 2017-10-03, at 12:49 AM, Mojca Miklavec wrote: > On 3 October 2017 at 05:01, Ken Cunningham wrote: >> if anyone would care to enlighten me on the best approach to making a VM for >> 10.5 intel, I would appreciate it. This is the only system I have t

perl module expert needed...

There is a rather fancy genome sequencing port submitted that is hung up on a few missing perl modules, if anyone can help Checking Required Perl Modules: XML::Compile::SOAP11 missing. Used for downloading sequence databases from RSAT

Re: perl module expert needed...

> On Oct 13, 2017, at 10:46 PM, Joshua Root wrote: > > > They're on CPAN: > > > > > What help do you need? > > - Josh I got bogged down in cpan2port and thought someone

Re: [macports-ports] branch master updated: macports-notifier: update to more recent version

On 2017-10-16, at 12:41 PM, Ryan Schmidt wrote: > However you have an Xcode-based build system, and I'm not certain how best to > supply variables to it at build time. I added this port recently, with exactly that potential use in mind: $ port search mulle mulle-xcode-settings @1.2.5 (devel)

Re: how to efficiently work through generating patches using git and macports build process?

> >cd $(port work foo) >cd foo-version >sudo git init . >sudo git add -A > >git diff > /tmp/my-patches.diff > > And more or less make sure that you don't do "sudo port -v install" > without, say the "-k" flag to keep the files before your run "git > diff". > This is

Re: how to efficiently work through generating patches using git and macports build process?

On 2017-08-30, at 9:41 AM, Michael Dickens wrote: > What Mojca wrote is what I do too. Simple but very effective! - MLD > Is there a way to make git ignore the *.o and *.a and other generated files that might be in the source tree that we're not interested in tracking -- or does the -A do

Re: how to efficiently work through generating patches using git and macports build process?

All this is very helpful. Thanks! Ken > Hope this helps! - MLD > > On Wed, Aug 30, 2017, at 12:50 PM, Ken Cunningham wrote: >> >> On 2017-08-30, at 9:41 AM, Michael Dickens wrote: >> >>> What Mojca wrote is what I do too. Simple but very effective! - ML

Re: New project member: kencu

Thanks very much, everyone of you, for the education over the past while. I appreciate your patience and wisdom. Glad to be part of the group! Best, Ken On 2017-09-11, at 6:26 AM, Rainer Müller wrote: > Please join us in welcoming the following new MacPorts project member: > &

"include" files in Portfiles - not PortGroups

Not meaning to engender too big of a discussion about how good an idea it might or might not be, but Is there a method for having a Portfile that does something like the following? -- # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4

specifying needs for qt ports

Hmm. Bit confusing, and these qt PortGroups are a little thin on documentation. I am working on a port that can build with qt4 or qt5 (any version). Looking through the PortGroups: the qmake 1.0 PortGroup sets up the build and calls the qt4 PortGroup the qt4 PortGroup sets up the proper

buildbot fetch of ghc fails on 10.8 or less due to SSL error

I have not seen this one here at home when installing ghc-bootstrap or ghc, but I presume it's due to the older SSL in MacPorts causing trouble: Error: Failed to fetch

Re: [macports-ports] branch master updated: mosh: allow build with systems < 10.7

> > This doesn't build on Lion: > > https://build.macports.org/builders/ports-10.7_x86_64_legacy-builder/builds/43805 > Noted. I was "sure" 10.7 had that capability, but it clearly doesn't at least on this build. I'll move the system test up to 10.8, once I verify that 10.8 built it.

Re: Macports Clang 3.9 compilation failures due to missing include

Hi Chris, Looking over the xrootd commit, and to hopefully make your life much easier when using the PortGroup cxx11 1.1, you generally don't need to do much of anything beyond adding the PortGroup. You can pretty much expect to delete all the other compiler selection components in your

buildbot force build a variant?

I'd like to force a build of webkit2-gtk +quartz on 15 & 16 to make sure my recent fixes play out as I think they will. After trying a few things, I can't seem to find the trick for that (if there is one). Is it possible to force a non-default build on the buildbot? Thanks, Ken

Re: buildbot force build a variant?

Ah, thanks very much for pointing out the ticket. I see now. I will stop trying things :> Ken On 2017-09-30, at 10:17 PM, Mojca Miklavec wrote: > > 30. sep. 2017 9:20 PM "Ken Cunningham" wrote: > I'd like to force a build of webkit2-gtk +quartz on 15 & 16 to ma

Re: [macports-ports] branch master updated: gnutls 3.5.15: add doc variant

argh blacklist { clang < 500 }, I meant On 2017-09-29, at 11:47 AM, Ken Cunningham wrote: >> But similar to cxx11 1.0, it doesn't do much on systems using libc++, i.e. >> 10.9 or later. >> > > The only thing it does if libc++ is selected is blacklist { clang > 500 } > and *gcc* > > Ken

Re: [macports-ports] branch master updated: gnutls 3.5.15: add doc variant

> But similar to cxx11 1.0, it doesn't do much on systems using libc++, i.e. > 10.9 or later. > The only thing it does if libc++ is selected is blacklist { clang > 500 } and *gcc* Ken

Re: [macports-ports] branch master updated: ghc and ghc-bootstrap: specify compiler to clang-4.0

On 2017-09-27, at 6:20 AM, Ryan Schmidt wrote: > > MacPorts automatically adds a build dependency on the compiler it uses, if > that compiler comes from MacPorts and if that dependency has not already been > added, so having already specified the compiler whitelist you don't then also > need

Re: Switching cxx_stdlib for C++11 on legacy macOS

On 2017-09-04, at 1:43 AM, Ryan Schmidt wrote: > > I have not followed the development of the cxx11 1.1 portgroup so I don't > know the benefits and drawbacks of using it compared to using libc++. After digging into this for a year and debugging and fixing a _great many_ ports, here are my

review requests

Hello, fellow MacPorts developers. While I am waiting for my commit permissions to be considered, I would appreciate anyone with some spare time and enthusiasm to consider a few PRs for committal/commission: Lout: a port update requested by a devoted MacPorts user on Sierra that needed to

Re: Switching cxx_stdlib for C++11 on legacy macOS (was: Re: [GSoC] migration)

> > As stupid as it seems but I don't see any cxx_stdlib option in my > macports.conf (see attached). base defaults it to stdlibc++ on <10.9, and libc++ on 10.9+ behind the scenes. > > Sure, this is a helpful point to keep in mind. Though, any reasons to not > switch to libc++? Although I

Re: Switching cxx_stdlib for C++11 on legacy macOS (was: Re: [GSoC] migration)

On 2017-09-02, at 11:04 AM, Ken Cunningham wrote: >> >> As stupid as it seems but I don't see any cxx_stdlib option in my >> macports.conf (see attached). > > base defaults it to stdlibc++ on <10.9, and libc++ on 10.9+ behind the > scenes. libstdc++ , not stdlibc++ haven't had coffee yet.

Re: Switching cxx_stdlib for C++11 on legacy macOS

On 2017-09-03, at 2:16 PM, db wrote: > > Wouldn't switching cxx_stdlib to and having the bots build binaries with > libc++ actually benefit both developers and users? > DIscussed absolutely to death. I use libc++ and would prefer we change to that. Everyone else is afraid of the

license question

I'm fixing up a submission for a piece of software called `profanity`. I think the license should be {GPL-3+ OpenSSLException} but I don't exactly know what OpenSSLException means. Do I have it right? Thanks. Ken Here is the blurb. = Profanity Copyright (C) 2012 - 2017 James Booth

Re: https fetch error on older (<10.9) OSX releases due to rejected protocol

Please see I Ken On 2017-10-18, at 12:39 PM, Christopher Jones wrote: > Hi, > > I just just been looking into a build failure on older OS in one set of > python ports, pyXY-bleach, that is a dependency of a port I maintain. > > It looks

how to build against an older SDK - library not found for -lcrt1.10.6.o

Hi, smart people. I'm trying to write up a Portfile (for TenFourFox) that requires building against an older SDK (10.4u) and I'm on 10.6 Intel. It's easy enough to pass in the sysroot configure.cxxflags-append -isysroot ${developer_dir}/SDKs/MacOSX10.4u.sdk

Re: how to build against an older SDK - library not found for -lcrt1.10.6.o

> > > Are you also using a 10.4 deployment target? > > - Josh I think that might be it. If you don't pass -macosx-version-min to the linker, it assumes 10.6. I'll work on that. Thanks, Ken

Re: [MacPorts] #55365: ttfautohint @1.7: new port

Sorry. Small hiccup slipped past me. Fixing it now. Ken > On Nov 23, 2017, at 4:49 PM, MacPorts <nore...@macports.org> wrote: > > #55365: ttfautohint @1.7: new port > --+--- > Reporter: tuffnatty | Owner:

homebrew's top 1000 requested installs

in case anyone is curious what people are requesting. MacPorts has almost all of these, I thought, glancing down the list. https://brew.sh/analytics/install-on-request/ Ken

Re: [macports-ports] branch master updated: PG snowleopard_fixes: don't require depends_lib-append

On 2017-12-04, at 9:26 AM, Ryan Schmidt wrote: >> +if {${snowleopard_fixes.addheader} eq "yes"} { >> +configure.cxxflags-append -include >> ${prefix}/include/snowleopardfixes.h >> +} > > > Is the header only needed for C++ code? Not for C code? > The header is almost never

Re: [macports-ports] branch master updated: PG snowleopard_fixes: don't require depends_lib-append

On 2017-12-04, at 10:07 AM, Ryan Schmidt wrote: > > My question was: does the header belong in cxxflags only? I assumed it should > also go in cflags. If that's wrong... why? > Oh, right. Yes, I think you're correct. The header, if needed, would be needed for C code as well. Good catch. I

help with generating a diff with svn for libcxx

I'm getting stuck generating a diff file for the changes made in revison 307461 of libcxx, so I can backport that into llvm-4.0 to fix the build of libcxx for PowerPC. I have checked out the llvm, libcxx, and libcxxabi sources using

Re: help with generating a diff with svn for libcxx

libcxx/commit/b2e9337b06425b4af554651d5f2fa65615eb009f.diff> Happy to learn the " right way" when anyone has time. Thanks, K On 2017-12-03, at 12:28 PM, Ken Cunningham wrote: > I'm getting stuck generating a diff file for the changes made in revison > 307461 of libcxx, so I can backport tha

Re: compiler selection on PPC

> On Dec 17, 2017, at 12:02 AM, Jeremy Huddleston Sequoia <jerem...@apple.com> > wrote: > > > >> On Dec 6, 2017, at 20:09, Ken Cunningham <ken.cunningham.web...@gmail.com> >> wrote: >> >> >>> On 2017-12-06, at 12:19 PM, Ken Cu

Re: Installing a Python wheel (whl) file using a port - Tensorflow

https://github.com/Homebrew/homebrew-core/blob/master/Formula/libtensorflow.rb On 2017-12-18, at 2:09 PM, Enrico Maria Crisostomo wrote: > Thanks Ken. > > Actually I checked brew and they haven't got a formula for TensorFlow (at > least at the moment). > > On 18 December 2017 at 22:57:42,

Re: Installing a Python wheel (whl) file using a port - Tensorflow

FYI, I recall homebrew has tensorflow, so you might get some hints looking at their formula. Marius was taking this on a few months ago as well, so might have some thoughts. Ken On 2017-12-18, at 1:52 PM, Enrico Maria Crisostomo wrote: > Hi, > > I’m trying to create a port for TensorFlow

Re: Build Failure on ports-10.6_i386_legacy: ocaml, py27-certifi, py27-mistune, py27-scandir, py27-tz, py27-zmq, root6, xrootd

I get the proper error message, as far as MacPorts allows at present: $ sudo port -v install ocaml ---> Computing dependencies for ocaml. ---> Fetching distfiles for ocaml Error: ocaml @4.05.0 requires OS X 10.7 or later. Error: Failed to fetch ocaml: incompatible OS X version Error: See

Re: [macports-ports] branch master updated: multiple ports: update maintainer

On 2017-12-13, at 8:29 AM, Ryan Schmidt wrote: >> -maintainers slor.net:james gmail.com:ken.cunningham.webuse >> openmaintainer >> +maintainers {kencu @kencu} openmaintainer > > Should James have been removed here? In your other changes, you're just > updating your own

I did something stupid and now can't uninstall a port

I have a port I'm working on, with a gui subport: sheepshaver sheepshaver-gui I accidentally made a typo installing the subport, and I typed this: sudo port -v install subport=sheepshaver=gui now I have a port installed like this: $ port -v installed | grep sheep sheepshaver=gui

Re: I did something stupid and now can't uninstall a port

n 12/19/2017 08:24 PM, Ken Cunningham wrote: >> I have a port I'm working on, with a gui subport: >> >> sheepshaver >> sheepshaver-gui >> >> I accidentally made a typo installing the subport, and I typed this: >> >> sudo port -v install

Re: Addressing Port submission failures on Travis

keep the master branch up to date, but leave your PR branch alone until it's merged, then delete the branch. > On Dec 19, 2017, at 11:54 PM, Andrew L. Moore wrote: > > I’m thinking that rebasing against my GitHub fork of MacPorts is what sent my > pull request into a tail

trace mode fails with sh: /usr/bin/tar: No such file or directory

I haven’t been able to use trace mode to test port installs because of the following error. Am I doing something wrong? $ sudo port -vst install poco ---> Fetching distfiles for poco ---> poco-1.6.0-all.tar.bz2 does not exist in /opt/local/var/macports/distfiles/poco ---> Attempting to

Re: trace mode fails with sh: /usr/bin/tar: No such file or directory

> On Dec 17, 2017, at 12:52 PM, Joshua Root <j...@macports.org> wrote: > > On 2017-12-18 07:18 , Ken Cunningham wrote: >> I haven’t been able to use trace mode to test port installs because of >> the following error. Am I doing something wrong? > > Aside fro

Re: gimp on HS

On 2017-11-13, at 9:16 AM, Rainer Müller wrote: > > regenerated with our patched version. The bug report [1] against > intltool never received any attention from upstream. > [1] https://bugs.launchpad.net/intltool/+bug/1197875 It's always amazing to me how anything less than an obsequious

add git dependency to github portgroup?

A recent commit of Dave's made me wonder if should we add a callback dependency for something like depends_build-appendbin:git:git to the github portgroup? I looked in there, expecting to see one, but didn't.

Re: add git dependency to github portgroup?

On 2017-11-20, at 9:21 AM, Joshua Root wrote: > On 2017-11-21 04:02 , Ken Cunningham wrote: >> A recent commit of Dave's made me wonder if should we add a callback >> dependency for something like >> >> depends_build-appendbin:git:git >> >> t

haskell base library >= 4.8 ?

Hi all, I'm updating hedgewars, and there is a build error (see below). The hedgewars devs say this means the base library is too old, and needs to be >= 4.8. I don't actually know what version of the haskell base library we have at present, or how to update it (if we can). Any ideas how that

Re: haskell base library >= 4.8 ?

ave changed, and ours says 2014.something.) Ken > On Nov 20, 2017, at 4:46 AM, Rainer Müller <rai...@macports.org> wrote: > >> On 2017-11-20 01:06, Ken Cunningham wrote: >> I'm updating hedgewars, and there is a build error (see below). The >> hedgewars devs say this

Re: how to build against an older SDK - library not found for -lcrt1.10.6.o

On 2017-11-15, at 8:49 AM, Ryan Schmidt wrote: > > > You don't need to do that manually. Just set "configure.sdk_version 10.4"; > MacPorts then adds the right -isysroot flags for you. > thanks. I will look into doing just that. And by the way, I'd like to have a chat one day with the fellow

Re: [macports-ports] branch master updated: util-linux: add snowleopardfixes

This ticket this fix came from predated the snowleopard_fixes portgroup. You're quite correct - since the portgroup was committed, that would be the proper fix now. -- K On Fri, Nov 10, 2017 at 5:59 PM, Ryan Schmidt wrote: > > On Oct 19, 2017, at 08:57, Kurt Hindenburg

interesting tool - deploymate - scans software for MacOS SDK needs

I thought I would mention a tool I came across recently that might be of some use to people on this list who are sometimes tasked with making software runnable on older systems. Deploymate scans source code for SDK dependencies, and will list certain MacOS SDK

  1   2   3   4   5   6   7   8   >