Hi,
On Thu, Jul 18, 2013 at 11:18:24AM +0200, Michael Wimmer wrote:
> Somehow my original question resulted in quite a debate about
> fundamental issues which I certainly did not intend ...
Sorry for going down that road, I just wanted to make sure nobody tries
to "do the right thing" and creates
Am 7/18/13 10:36 AM, schrieb Clemens Lang:
> Hi,
>
> On Wed, Jul 17, 2013 at 08:14:15PM -0400, Lawrence Velázquez wrote:
>> No one said anything about Python +gccXY variants in that thread. If
>> the maintainers of the Python ports can be convinced to add such
>> variants (or to create subports so
Hi,
On Wed, Jul 17, 2013 at 08:14:15PM -0400, Lawrence Velázquez wrote:
> No one said anything about Python +gccXY variants in that thread. If
> the maintainers of the Python ports can be convinced to add such
> variants (or to create subports so that other ports could depend on
> them), that woul
On Jul 17, 2013, at 8:14 PM, Lawrence Velázquez wrote:
> No one said anything about Python +gccXY variants in that thread. If the
> maintainers of the Python ports can be convinced to add such variants (or to
> create subports so that other ports could depend on them), that would be fine.
I me
On Jul 17, 2013, at 6:47 PM, Michael Wimmer wrote:
> There is no gcc variant of python, and as argued in a recent thread on the
> macports mailing list (
> https://lists.macosforge.org/pipermail/macports-users/2013-June/032891.html),
> this is not going to changed.
No one said anything about Py
> > You are correct in the general case but not in this particular special
> case, and the Python and Perl extension mechanisms force the compiler for
> very good reasons.
>
> And MacPorts forces the compiler for very good reasons. The very specific
> problem that this Python decision causes for Ma
On Wed, Jul 17, 2013 at 6:13 PM, Ryan Schmidt wrote:
> On Jul 17, 2013, at 08:56, Brandon Allbery wrote:
> > You are correct in the general case but not in this particular special
> case, and the Python and Perl extension mechanisms force the compiler for
> very good reasons.
>
> And MacPorts forc
On Jul 17, 2013, at 08:56, Brandon Allbery wrote:
> You are correct in the general case but not in this particular special case,
> and the Python and Perl extension mechanisms force the compiler for very good
> reasons.
And MacPorts forces the compiler for very good reasons. The very specific
On Wed, Jul 17, 2013 at 11:15 AM, Daniel J. Luke wrote:
> On Jul 17, 2013, at 9:56 AM, Brandon Allbery wrote:
> > On Wed, Jul 17, 2013 at 6:55 AM, Ryan Schmidt
> wrote:
> > On Jul 17, 2013, at 04:28, Michael Wimmer wrote:
> > >> If the build does not respect the compiler choice, that is a bug
On Jul 17, 2013, at 9:56 AM, Brandon Allbery wrote:
>
> On Wed, Jul 17, 2013 at 6:55 AM, Ryan Schmidt wrote:
> On Jul 17, 2013, at 04:28, Michael Wimmer wrote:
> >> If the build does not respect the compiler choice, that is a bug that
> >> should be fixed.
> >
> > thanks for your answer, I und
On Wed, Jul 17, 2013 at 6:55 AM, Ryan Schmidt wrote:
> On Jul 17, 2013, at 04:28, Michael Wimmer wrote:
> >> If the build does not respect the compiler choice, that is a bug that
> should be fixed.
> >
> > thanks for your answer, I understand that this is how it should be done
> > in general. How
On Jul 17, 2013, at 04:28, Michael Wimmer wrote:
>
>> If you want to use gfortran, you need to use a compiler that has it, like
>> the gcc ports. Add variants allowing the user to choose which one, and
>> default to 4.7:
>>
>> https://trac.macports.org/wiki/PortfileRecipes#gcc
>>
>> If the
> If you want to use gfortran, you need to use a compiler that has it, like the
> gcc ports. Add variants allowing the user to choose which one, and default to
> 4.7:
>
> https://trac.macports.org/wiki/PortfileRecipes#gcc
>
> If the build does not respect the compiler choice, that is a bug tha
On Jul 17, 2013, at 04:18, Michael Wimmer wrote:
> I want to write a Portfile for a python package that (amongst other
> things) interfaces to a Fortran library.
>
> To that extent, there are some C-files there that have to be compiled
> and then linked to the library under question, and then in
Hi all,
I want to write a Portfile for a python package that (amongst other
things) interfaces to a Fortran library.
To that extent, there are some C-files there that have to be compiled
and then linked to the library under question, and then in addition also
to libgfortran (since it's C code). T
15 matches
Mail list logo
