I committed it.
David
On Tue, Apr 3, 2018 at 12:40 PM, Peter Brommer
wrote:
> Hi Mojca,
>
> thanks for the suggestion. In my defence, I’m following the (obviously
> out-of-date) guide at https://trac.macports.org/wiki/howto/Upgrade but
> I’ll try and use the pull requests for future updates. Ho
pypi:p/pybtex did not work for me. "port fetch" failed. Does it really work
for you?
On Mon, Apr 30, 2018 at 10:00 PM, Ryan Schmidt
wrote:
>
> On Apr 30, 2018, at 23:17, David Strubbe wrote:
>
> > David Strubbe (dstrubbe) pushed a commit to branch master
> &g
It timed out, on several tries. Maybe this was some temporary outage or
local problem here. Anyway, I'll put it back.
On Mon, Apr 30, 2018 at 10:44 PM, Joshua Root wrote:
> On 2018-5-1 15:22 , David Strubbe wrote:
> > pypi:p/pybtex did not work for me. "port fetch"
Hello Mark,
I think you may have a basic misunderstanding here. The compilers portgroup
provides variants that select compilers, rather than being a way to select
the compiler in the portfile. It will provide gcc/gfortran (in specific
versions). If something like clang doesn't work, you remove it
ebug:build (procedure "portbuild::build_main" line 8)
> :debug:build invoked from within
> :debug:build "$procedure $targetname"
>
>
> whereas adding a whitelist succeeds (using gfortran):
>
> compiler.whitelist macports-gcc-11
> compilers.choose
If the compilers need to be consistent, then you can use the compilers
portgroup to enforce that.
David
On Wed, Nov 1, 2017 at 10:29 AM, Mojca Miklavec wrote:
> Hi,
>
> I'm currently trying to fix wxWidgets-3.0 in various ways. One of the
> problems of the latest release is that it compiles fin
Good point. This does work, but for simplicity I'll fix that.
David
On Thu, Nov 9, 2017 at 1:49 PM, Ryan Schmidt
wrote:
>
> On Nov 9, 2017, at 13:48, David Strubbe wrote:
>
> > David Strubbe (dstrubbe) pushed a commit to branch master
> > in repository macport
Hello all,
I have a question about the muniversal port group, motivated by examining
what happens with its usage in the fftw-3 port. If the +universal variant
is selected, then appropriate values of configure.args are set for
different architectures via merger_configure_args, which in the case of
I see, thanks for the clarifications.
David
On Fri, Feb 9, 2018 at 12:14 PM, Joshua Root wrote:
> On 2018-2-10 07:04 , Joshua Root wrote:
> > On 2018-2-10 06:14 , David Strubbe wrote:
> >> Hello all,
> >>
> >> I have a question about the muniversal port gro
I suggest a port crane (to fit with our name), e.g.
https://www.tripadvisor.com/LocationPhotoDirectLink-g32810-i36315229-Oakland_California.html
David
On Wed, Feb 21, 2018 at 12:38 PM, Ken Cunningham <
ken.cunningham.web...@gmail.com> wrote:
>
> On 2018-02-21, at 12:36 PM, Dave Horsfall wrote:
>
Hi Ryan,
I would just like to point out regarding testsuites that it can sometimes
happen in my experience for the test phase to fail because of a problem in
packaging rather than an inherent problem in the source. For example,
something wasn't linked properly, and the way a library was passed to
11 matches
Mail list logo
