I notice homebrew is forcing the installation of binaries built on their 10.12
or 10.13 builders onto 10.14 to get around the 32bit build problem on 10.14.
I don't believe there is any way to force our binary installer to install older
system builds in the same way -- but if there was, it would
On 2018-10-29 10:49 , Mark Brethen wrote:
> There is no python setup file. The makefile uses python-config to get
> the path to the python header files. When port select sets python to
> none, it builds with apple python 2.7 without error. When port select
> sets python to python27 it fails because
There is no python setup file. The makefile uses python-config to get the path
to the python header files. When port select sets python to none, it builds
with apple python 2.7 without error. When port select sets python to python27
it fails because it cannot find a python setup.
In the termina
Mark Brethenmark.bret...@gmail.com
On Oct 28, 2018, at 5:46 PM, Ryan Schmidt wrote:setup.py is where a python project defines how it is to be set up. It's like a configure file. It's specific to each project. There isn't a default. Maybe for this software the configure
> On Oct 28, 2018, at 5:46 PM, Ryan Schmidt wrote:
>
>
>
> On Oct 28, 2018, at 16:50, Mark Brethen wrote:
>
>> brethen-air:~ marbre$ port select --summary
>> Warning: port definitions are more than two weeks old, consider updating
>> them by running 'port selfupdate'.
>> Name Selected
On Oct 28, 2018, at 16:50, Mark Brethen wrote:
> brethen-air:~ marbre$ port select --summary
> Warning: port definitions are more than two weeks old, consider updating them
> by running 'port selfupdate'.
> Name Selected Options
> ===
> clang none
On 2018-10-29 09:03 , Mark Brethen wrote:
> It looks to me that it failed because the source does not provide a
> ‘setup.py’ configuration file. Apple must provide a default setup.
The python portgroup is for software that builds with a setup.py. If
this software doesn't have one, don't use it.
It looks to me that it failed because the source does not provide a ‘setup.py’
configuration file. Apple must provide a default setup.
Mark Brethen
mark.bret...@gmail.com
> On Oct 28, 2018, at 4:50 PM, Mark Brethen wrote:
>
> brethen-air:~ marbre$ port select --summary
> Warning: port defini
brethen-air:~ marbre$ port select --summary
Warning: port definitions are more than two weeks old, consider updating them
by running 'port selfupdate'.
Name Selected Options
===
clang none mp-clang-6.0 none
cython none cython36 non
brethen-air:~ marbre$ port select --summary
Name Selected Options
===
clang none mp-clang-6.0 none
cython none cython36 none
gccnone mp-gcc7 none
ipythonpy34-ipython none
llvm none mp-llvm-3.4 mp
I didn’t seem to matter. I tried both python27 and 36.
Mark Brethen
mark.bret...@gmail.com
> On Oct 28, 2018, at 4:08 PM, Mark Brethen wrote:
>
> Quite by accident I have discovered a flaw with my libreduce port as regards
> to "port select —set python". I had not set a default python versi
On Oct 28, 2018, at 16:08, Mark Brethen wrote:
> Quite by accident I have discovered a flaw with my libreduce port as regards
> to "port select —set python". I had not set a default python version before I
> built the reduce libraries, unaware it was using apple's system python 2.7 to
> buil
I’ll try to be more specific. This python source does not seem to set the build
env. and I don’t see how the python port group will do that. I think the build
command needs to set be to "./qreduce.py” and the library path set in
“qrmodel.py”. Do I understand this correctly?
Mark Brethen
mark.br
One way to make this easy and a priori trouble free is to modify the PortGroup
command such files in $portdir or $filespath have priority over those int the
normal PG directory (and don't advertise the new feature widely).
In fact I should look at how PGs are loaded and if they behave as expect
On Oct 28, 2018, at 03:39, René J.V. Bertin wrote:
> Maybe describe how to achieve this on the Recipes page, along with the other
> sometimes-useful tricks?
I don't think we want to publish a recipe on how to include files, because I
don't think we want people to do it.
On Saturday October 27 2018 17:52:15 Ryan Schmidt wrote:
>We could re-add it, or maybe change the source command to work how the include
>command used to work. But I'm not convinced that we should do that. There
>aren't many reasons why an include file would be useful, and we evidently
>haven't
On Sat, 27 Oct 2018 at 20:06, Ryan Schmidt wrote:
> On Oct 27, 2018, at 12:53, Mojca Miklavec wrote:
> > On Fri, 26 Oct 2018 at 23:26, Joshua Root wrote:
> >
> >> let's assume
> >> something else is going on here. Is there an actual circular dependency?
> >
> > That's why I came up to ask for someo
17 matches
Mail list logo