Re: Trac down?
On 11.02.2016 08:38 PM, Ryan Schmidt wrote: > There was high memory usage for an unknown reason, which caused the OS to > start killing processes, including the web server, to free memory. I rebooted > the server and it's working again. Thanks for that, but Trac has also stopped updating after r145635 (which coincidences with my first SVN file property change in r145636.) Mihai signature.asc Description: OpenPGP digital signature ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Trac down?
There was high memory usage for an unknown reason, which caused the OS to start killing processes, including the web server, to free memory. I rebooted the server and it's working again. > On Feb 11, 2016, at 12:59, Craig Treleaven wrote: > > It seems that https://trac.macports.org is unreachable. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Trac down?
On 11.02.2016 07:59 PM, Craig Treleaven wrote: > It seems that https://trac.macports.org is unreachable. SVN as such still works. I think I broke it with a few SVN prop updates on files, but not too sure about this. CCing Ryan. Mihai signature.asc Description: OpenPGP digital signature ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Trac down?
It seems that https://trac.macports.org is unreachable. Craig ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: CFITSIO's Fortran interface
On Feb 11, 2016, at 2:00 AM, Sébastien Maret wrote: > > >> Le 10 févr. 2016 à 16:23, Ryan Schmidt a écrit : >> >> On Feb 10, 2016, at 8:52 AM, Sébastien Maret wrote: >> >>> I am maintaining the Gildas port which depends on the CFITSIO library. >>> CFITSIO has a Fortran interface but it is not built by default: one need to >>> select a specific variant (e.g. +gcc 5) for this. This is a problem for the >>> Gildas because the compilation fails without the Fortran interface: >>> https://trac.macports.org/ticket/50543 >>> >>> Is there a way for a port to depend on a specific variant of another port? >>> If not then how can I solve this? >> >> The require_active_variants procedure in the active_variants 1.1 port group. > > Thanks. I’ve added the cfitsio +gcc5 in require_active_variants and this > solves the problem on Yosemite: > https://trac.macports.org/changeset/145605 > > However the compilation fails on older MacOS versions because the +gcc5 > variant is not available. Why isn't the gcc5 variant available on older Mac OS versions? > I don’t need the gcc5 variant in particular; any of the gcc4x should be fine. > How can I do this with require_active_variants? At present, it doesn't offer that functionality. You could code it manually, if it's truly required to have different gcc variants available on different versions of OS X, though this would be the first circumstance I've heard of of that being necessary. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: CFITSIO's Fortran interface
> Le 10 févr. 2016 à 16:23, Ryan Schmidt a écrit : > > On Feb 10, 2016, at 8:52 AM, Sébastien Maret wrote: > >> I am maintaining the Gildas port which depends on the CFITSIO library. >> CFITSIO has a Fortran interface but it is not built by default: one need to >> select a specific variant (e.g. +gcc 5) for this. This is a problem for the >> Gildas because the compilation fails without the Fortran interface: >> https://trac.macports.org/ticket/50543 >> >> Is there a way for a port to depend on a specific variant of another port? >> If not then how can I solve this? > > The require_active_variants procedure in the active_variants 1.1 port group. Thanks. I’ve added the cfitsio +gcc5 in require_active_variants and this solves the problem on Yosemite: https://trac.macports.org/changeset/145605 However the compilation fails on older MacOS versions because the +gcc5 variant is not available. I don’t need the gcc5 variant in particular; any of the gcc4x should be fine. How can I do this with require_active_variants? Sébastien ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
