Re: Processing of port freecad fails
Ryan Schmidt writes: > On Jan 9, 2015, at 1:34 PM, Sean Farley wrote: >> >> Ryan Schmidt writes: >> >>> On Jan 9, 2015, at 1:16 PM, Marius Schamschula wrote: freecad used to declare +gcc48 as the default variant until https://trac.macports.org/changeset/130949 was committed. Given that this change set deleted fortran related default variants for a number of packages, we will likely hear about these in the near future. >>> >>> Actually, in that revision, setting the default compiler variant was moved >>> from the individual portfiles to the compilers portgroup. >>> >>> Then in r130953 the default was changed from gcc48 to gcc49. But what about >>> the ports like freecad that don't have a gcc49 variant? >> >> Welp, that's unintended. In cases like these, I imagined portfile >> authors would override and add their own default variant. I'm a little >> busy now, so if someone feels encouraged they can add it back. >> >> A longer term fix would be to test for gcc49 and work backwards to >> gcc48, etc. >> >> Is there a reason why +gfortran was left out? > > My guess is that a gcc49 variant could be added to freecad and that it would > work fine. I guess gcc49 wasn't stable when freecad's default of gcc48 was > chosen. But if you're leaving it up to each port to decide which variants to > provide, then you have to either let each port decide which of them is the > default, or else have much more intelligent logic in the portgroup to pick > the "best" one as the default, and not make assumptions about which variants > exist. I agree. I'll update the portgroup accordingly. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Processing of port freecad fails
On Jan 9, 2015, at 1:34 PM, Sean Farley wrote: > > Ryan Schmidt writes: > >> On Jan 9, 2015, at 1:16 PM, Marius Schamschula wrote: >>> >>> freecad used to declare +gcc48 as the default variant until >>> https://trac.macports.org/changeset/130949 was committed. Given that this >>> change set deleted fortran related default variants for a number of >>> packages, we will likely hear about these in the near future. >> >> Actually, in that revision, setting the default compiler variant was moved >> from the individual portfiles to the compilers portgroup. >> >> Then in r130953 the default was changed from gcc48 to gcc49. But what about >> the ports like freecad that don't have a gcc49 variant? > > Welp, that's unintended. In cases like these, I imagined portfile > authors would override and add their own default variant. I'm a little > busy now, so if someone feels encouraged they can add it back. > > A longer term fix would be to test for gcc49 and work backwards to > gcc48, etc. > > Is there a reason why +gfortran was left out? My guess is that a gcc49 variant could be added to freecad and that it would work fine. I guess gcc49 wasn't stable when freecad's default of gcc48 was chosen. But if you're leaving it up to each port to decide which variants to provide, then you have to either let each port decide which of them is the default, or else have much more intelligent logic in the portgroup to pick the "best" one as the default, and not make assumptions about which variants exist. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Processing of port freecad fails
Ryan Schmidt writes: > On Jan 9, 2015, at 1:16 PM, Marius Schamschula wrote: >> >> freecad used to declare +gcc48 as the default variant until >> https://trac.macports.org/changeset/130949 was committed. Given that this >> change set deleted fortran related default variants for a number of >> packages, we will likely hear about these in the near future. > > Actually, in that revision, setting the default compiler variant was moved > from the individual portfiles to the compilers portgroup. > > Then in r130953 the default was changed from gcc48 to gcc49. But what about > the ports like freecad that don't have a gcc49 variant? Welp, that's unintended. In cases like these, I imagined portfile authors would override and add their own default variant. I'm a little busy now, so if someone feels encouraged they can add it back. A longer term fix would be to test for gcc49 and work backwards to gcc48, etc. Is there a reason why +gfortran was left out? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Processing of port freecad fails
On Jan 9, 2015, at 1:16 PM, Marius Schamschula wrote: > > freecad used to declare +gcc48 as the default variant until > https://trac.macports.org/changeset/130949 was committed. Given that this > change set deleted fortran related default variants for a number of packages, > we will likely hear about these in the near future. Actually, in that revision, setting the default compiler variant was moved from the individual portfiles to the compilers portgroup. Then in r130953 the default was changed from gcc48 to gcc49. But what about the ports like freecad that don't have a gcc49 variant? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Processing of port freecad fails
On Jan 9, 2015, at 12:52 PM, Ryan Schmidt wrote: > > On Jan 8, 2015, at 8:40 PM, Eneko Gotzon wrote: > >> ---> Fetching distfiles for freecad >> Error: org.macports.fetch for port freecad returned: must set at least one >> fortran variant >> >> freecad has these variants: >> debug: Enable debug binaries >> gcc48: Build using the MacPorts gcc 4.8 compiler >> universal: Build for multiple architectures >> >> Please, >> • What must I choose? >> • What exact command must I run? > > The error message says you must set a fortran variant. > > The only one of those variants that has to do with fortran is gcc48, so you > should run: > > sudo port clean freecad > sudo port install freecad +gcc48 > > It is unclear to me why freecad does not declare +gcc48 a default variant, or > why indeed if fortran is required it is offered as a "variant" at all. > Variants are used for options the user may choose to enable or disable, but > in this case it sounds like the user does not actually have any choice at > all, and so should not be offered one. freecad used to declare +gcc48 as the default variant until https://trac.macports.org/changeset/130949 was committed. Given that this change set deleted fortran related default variants for a number of packages, we will likely hear about these in the near future. Marius -- Marius Schamschula ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Processing of port freecad fails
On Jan 8, 2015, at 8:40 PM, Eneko Gotzon wrote: > ---> Fetching distfiles for freecad > Error: org.macports.fetch for port freecad returned: must set at least one > fortran variant > > freecad has these variants: >debug: Enable debug binaries >gcc48: Build using the MacPorts gcc 4.8 compiler >universal: Build for multiple architectures > > Please, > • What must I choose? > • What exact command must I run? The error message says you must set a fortran variant. The only one of those variants that has to do with fortran is gcc48, so you should run: sudo port clean freecad sudo port install freecad +gcc48 It is unclear to me why freecad does not declare +gcc48 a default variant, or why indeed if fortran is required it is offered as a "variant" at all. Variants are used for options the user may choose to enable or disable, but in this case it sounds like the user does not actually have any choice at all, and so should not be offered one. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Processing of port freecad fails
Hello Future Shapers! ---> Fetching distfiles for freecad Error: org.macports.fetch for port freecad returned: must set at least one fortran variant freecad has these variants: debug: Enable debug binaries gcc48: Build using the MacPorts gcc 4.8 compiler universal: Build for multiple architectures Please, - What must I choose? - What exact command must I run? Thank you very much! Main log attached. -- Eneko Gotzon Ares main.log Description: Binary data ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
