Re: Compilers and MPI Port Groups
s...@macports.org writes:
> ebori...@ieee.org writes:
>
>> Haven't had a chance to look into this; have you updated mpich-devel
>> (betas / etc), as well?
>
> Yep. The two files are almost the same now and could even be merged into
> one portfile to de-duplicate logic. Same goes for openmpi{,-devel}.
>
> The noteworthy changesets are:
>
> mpi-doc: new port to abstract docs for mpich and openmpi
> https://smf.io/macports/changeset/2d0f20f8414b7b676f0c72079938ff3fc6dccb86
>
> mpich_select: rename to mpi_select so all mpi ports can use it
> https://smf.io/macports/changeset/0946ba1629b857a1cc3ca5ae098df616c30dc2a4
>
> mpich: use non-conflicting names for files that mpich-devel also installs
> https://smf.io/macports/changeset/718a0fc09fedb2c24a662e833fe286f945d30135
>
> mpich-devel: make non-conflicting with mpich
> https://smf.io/macports/changeset/040299c685f3a453987bd7dadefe2882eb52bd9a
>
> openmpi: unify wrapper names as mpi{cc,cxx,fc,f77,f90}
> https://smf.io/macports/changeset/e6453dc62852bd9f2b6b902bb018f8bdb75d5970
Just a heads up that I'm planning to push this tomorrow.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Compilers and MPI Port Groups
ebori...@ieee.org writes:
> Haven't had a chance to look into this; have you updated mpich-devel
> (betas / etc), as well?
Yep. The two files are almost the same now and could even be merged into
one portfile to de-duplicate logic. Same goes for openmpi{,-devel}.
The noteworthy changesets are:
mpi-doc: new port to abstract docs for mpich and openmpi
https://smf.io/macports/changeset/2d0f20f8414b7b676f0c72079938ff3fc6dccb86
mpich_select: rename to mpi_select so all mpi ports can use it
https://smf.io/macports/changeset/0946ba1629b857a1cc3ca5ae098df616c30dc2a4
mpich: use non-conflicting names for files that mpich-devel also installs
https://smf.io/macports/changeset/718a0fc09fedb2c24a662e833fe286f945d30135
mpich-devel: make non-conflicting with mpich
https://smf.io/macports/changeset/040299c685f3a453987bd7dadefe2882eb52bd9a
openmpi: unify wrapper names as mpi{cc,cxx,fc,f77,f90}
https://smf.io/macports/changeset/e6453dc62852bd9f2b6b902bb018f8bdb75d5970
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Compilers and MPI Port Groups
lar...@macports.org writes:
> On Jan 19, 2014, at 6:41 PM, Sean Farley wrote:
>
>> Any objections before I push?
>
> Not sure they're "objections" so much as "nitpicks".
Any helpful feedback is appreciated!
>> set compilers.list {cc cxx cpp objc fc f77 f90}
>
> There's a "configure.objcxx" option now.
Ah, awesome. I'll add that too.
>> # dragonegg versions will always match the corresponding clang version
>> foreach v ${clang_versions} {
>
> This can no longer be enforced, as the dragonegg-3.5* ports were removed in
> r115969.
Woah, I completely missed that. Thanks for the heads up.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Compilers and MPI Port Groups
On Jan 19, 2014, at 6:41 PM, Sean Farley wrote:
> Any objections before I push?
Not sure they're "objections" so much as "nitpicks".
> set compilers.list {cc cxx cpp objc fc f77 f90}
There's a "configure.objcxx" option now.
> # dragonegg versions will always match the corresponding clang version
> foreach v ${clang_versions} {
This can no longer be enforced, as the dragonegg-3.5* ports were removed in
r115969.
vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Compilers and MPI Port Groups
Go for it! I want to see how it turns out. On Sun, Jan 19, 2014 at 6:41 PM, Sean Farley wrote: > > s...@macports.org writes: > > > s...@macports.org writes: > > > >> s...@macports.org writes: > >> > >>> Hello all and Happy Boxing Day! > >>> > >>> I have done a complete rewrite of the compilers and mpi port groups > >>> based on suggestions from previous emails. I will try to keep this > email > >>> short and provide links for those that want to know more. > >>> > >>> Highlights: > >>> > >>> - specify which compilers to set via compilers.choose, > >>> e.g. 'compilers.choose f77 f90 fc' > >>> > >>> - functions for testing if fortran has been selected for optional > >>> interfaces > >>> > >>> - portfile author can specify if fortran (or mpi) is required > >>> > >>> - unified and have made non-conflicting openmpi and mpich ports; also > >>> added an openmpi-devel port [1] > >>> > >>> - can now select either mpi port as the default mpi installation > >>> > >>> Example of a portfile using the new compilers portgroup: > >>> https://smf.io/macports/changeset/compilers > >>> > >>> Example of a portfile that uses the mpi portgroup: > >>> https://smf.io/macports/files/mpi/dports/science/hdf5-18/Portfile > >>> > >>> The changes I made to the sparskit and hdf5-18 portfiles are just > >>> examples I did for illustrative purposes. I won't push them unless the > >>> portfile author wants it. The mpich and openmpi portfiles need these > >>> changes so that the mpi portgroup will work. > >>> > >>> Anyway, I'd like to push this soon so that I can continue other work > >>> (and close a lot of tickets), so it'd be great if others could take a > >>> look at the proposed changes. > >>> > >>> [1] https://smf.io/macports/changeset/81bb51 or look at the changelog > >>> https://smf.io/macports/changelog to see all the diffs > >> > >> Just an update to say that I've gone ahead and finished updating all the > >> ports that use mpi to use this new port group. The only work that needs > >> to be done is to get some review of this patch series and after that, > >> permission to push. > >> > >> I've cc'd the people who are the maintainers of the ports I changed, > >> listed below. It'd be great to have you guys look at the changes. > >> > >> dstrubbe: sparskit, hpl, octopus > >> > >> eborisch: mpich > >> > >> mww: openmpi > >> > >> raimue: valgrind, valgrind-devel > >> > >> takeshi: berkeley_upc, omnixmp, gnudatalanguage, netcdf, netcdf-cxx, > >> netcdf-cxx4, netcdf-fortran > >> > >> mmoll: optpp, hdf5-18, arpack > >> > >> hum: plda > >> > >> howarth: apbs-mpi > >> > >> mattoates: raxml > >> > >> mk: scotch > >> > >> michaelld: SuiteSparse > >> > >> Check out http://smf.io/macports for the updated changes. > >> > >> Having other people look at this would be great and hopefully would > >> catch some of the errors I missed. The common ones I noticed were > >> missing revbumps (though, I think I got all of those now). > >> > >> Documentation is very much "read the comments and the code itself or > >> look at an example" so, apologies about that. Also, sometimes I couldn't > >> think of a good name for a proc, so if anyone has a better name, please > >> speak up. > >> > >> Some changes since last email are: > >> > >> - ensure the same mpi is used via mpi.enforce_variant > >> > >> - ensure the same c compiler is used (even when using mpi) via > >> compilers.enforce_c > >> > >> - similar for fortran, compilers.enforce_fortran > >> > >> - test for avx compatible compiler via avx_variant_isset > >> > >> Still yet to be done is to replace all custom recipes done for the > >> compiler variants. By my count, there are no more than 72 of those > >> ports. This is lower priority since they'll still work as is. > > > > If nobody has any objections to this, I was hoping to push this in a few > days. > > Any objections before I push? I guess at this point the errors that are > left are of the type that one finds after trying to get the buildbot to > compile a port. > ___ > macports-dev mailing list > macports-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-dev > ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Compilers and MPI Port Groups
s...@macports.org writes: > s...@macports.org writes: > >> s...@macports.org writes: >> >>> Hello all and Happy Boxing Day! >>> >>> I have done a complete rewrite of the compilers and mpi port groups >>> based on suggestions from previous emails. I will try to keep this email >>> short and provide links for those that want to know more. >>> >>> Highlights: >>> >>> - specify which compilers to set via compilers.choose, >>> e.g. 'compilers.choose f77 f90 fc' >>> >>> - functions for testing if fortran has been selected for optional >>> interfaces >>> >>> - portfile author can specify if fortran (or mpi) is required >>> >>> - unified and have made non-conflicting openmpi and mpich ports; also >>> added an openmpi-devel port [1] >>> >>> - can now select either mpi port as the default mpi installation >>> >>> Example of a portfile using the new compilers portgroup: >>> https://smf.io/macports/changeset/compilers >>> >>> Example of a portfile that uses the mpi portgroup: >>> https://smf.io/macports/files/mpi/dports/science/hdf5-18/Portfile >>> >>> The changes I made to the sparskit and hdf5-18 portfiles are just >>> examples I did for illustrative purposes. I won't push them unless the >>> portfile author wants it. The mpich and openmpi portfiles need these >>> changes so that the mpi portgroup will work. >>> >>> Anyway, I'd like to push this soon so that I can continue other work >>> (and close a lot of tickets), so it'd be great if others could take a >>> look at the proposed changes. >>> >>> [1] https://smf.io/macports/changeset/81bb51 or look at the changelog >>> https://smf.io/macports/changelog to see all the diffs >> >> Just an update to say that I've gone ahead and finished updating all the >> ports that use mpi to use this new port group. The only work that needs >> to be done is to get some review of this patch series and after that, >> permission to push. >> >> I've cc'd the people who are the maintainers of the ports I changed, >> listed below. It'd be great to have you guys look at the changes. >> >> dstrubbe: sparskit, hpl, octopus >> >> eborisch: mpich >> >> mww: openmpi >> >> raimue: valgrind, valgrind-devel >> >> takeshi: berkeley_upc, omnixmp, gnudatalanguage, netcdf, netcdf-cxx, >> netcdf-cxx4, netcdf-fortran >> >> mmoll: optpp, hdf5-18, arpack >> >> hum: plda >> >> howarth: apbs-mpi >> >> mattoates: raxml >> >> mk: scotch >> >> michaelld: SuiteSparse >> >> Check out http://smf.io/macports for the updated changes. >> >> Having other people look at this would be great and hopefully would >> catch some of the errors I missed. The common ones I noticed were >> missing revbumps (though, I think I got all of those now). >> >> Documentation is very much "read the comments and the code itself or >> look at an example" so, apologies about that. Also, sometimes I couldn't >> think of a good name for a proc, so if anyone has a better name, please >> speak up. >> >> Some changes since last email are: >> >> - ensure the same mpi is used via mpi.enforce_variant >> >> - ensure the same c compiler is used (even when using mpi) via >> compilers.enforce_c >> >> - similar for fortran, compilers.enforce_fortran >> >> - test for avx compatible compiler via avx_variant_isset >> >> Still yet to be done is to replace all custom recipes done for the >> compiler variants. By my count, there are no more than 72 of those >> ports. This is lower priority since they'll still work as is. > > If nobody has any objections to this, I was hoping to push this in a few days. Any objections before I push? I guess at this point the errors that are left are of the type that one finds after trying to get the buildbot to compile a port. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Compilers and MPI Port Groups
s...@macports.org writes: > s...@macports.org writes: > >> Hello all and Happy Boxing Day! >> >> I have done a complete rewrite of the compilers and mpi port groups >> based on suggestions from previous emails. I will try to keep this email >> short and provide links for those that want to know more. >> >> Highlights: >> >> - specify which compilers to set via compilers.choose, >> e.g. 'compilers.choose f77 f90 fc' >> >> - functions for testing if fortran has been selected for optional >> interfaces >> >> - portfile author can specify if fortran (or mpi) is required >> >> - unified and have made non-conflicting openmpi and mpich ports; also >> added an openmpi-devel port [1] >> >> - can now select either mpi port as the default mpi installation >> >> Example of a portfile using the new compilers portgroup: >> https://smf.io/macports/changeset/compilers >> >> Example of a portfile that uses the mpi portgroup: >> https://smf.io/macports/files/mpi/dports/science/hdf5-18/Portfile >> >> The changes I made to the sparskit and hdf5-18 portfiles are just >> examples I did for illustrative purposes. I won't push them unless the >> portfile author wants it. The mpich and openmpi portfiles need these >> changes so that the mpi portgroup will work. >> >> Anyway, I'd like to push this soon so that I can continue other work >> (and close a lot of tickets), so it'd be great if others could take a >> look at the proposed changes. >> >> [1] https://smf.io/macports/changeset/81bb51 or look at the changelog >> https://smf.io/macports/changelog to see all the diffs > > Just an update to say that I've gone ahead and finished updating all the > ports that use mpi to use this new port group. The only work that needs > to be done is to get some review of this patch series and after that, > permission to push. > > I've cc'd the people who are the maintainers of the ports I changed, > listed below. It'd be great to have you guys look at the changes. > > dstrubbe: sparskit, hpl, octopus > > eborisch: mpich > > mww: openmpi > > raimue: valgrind, valgrind-devel > > takeshi: berkeley_upc, omnixmp, gnudatalanguage, netcdf, netcdf-cxx, > netcdf-cxx4, netcdf-fortran > > mmoll: optpp, hdf5-18, arpack > > hum: plda > > howarth: apbs-mpi > > mattoates: raxml > > mk: scotch > > michaelld: SuiteSparse > > Check out http://smf.io/macports for the updated changes. > > Having other people look at this would be great and hopefully would > catch some of the errors I missed. The common ones I noticed were > missing revbumps (though, I think I got all of those now). > > Documentation is very much "read the comments and the code itself or > look at an example" so, apologies about that. Also, sometimes I couldn't > think of a good name for a proc, so if anyone has a better name, please > speak up. > > Some changes since last email are: > > - ensure the same mpi is used via mpi.enforce_variant > > - ensure the same c compiler is used (even when using mpi) via > compilers.enforce_c > > - similar for fortran, compilers.enforce_fortran > > - test for avx compatible compiler via avx_variant_isset > > Still yet to be done is to replace all custom recipes done for the > compiler variants. By my count, there are no more than 72 of those > ports. This is lower priority since they'll still work as is. If nobody has any objections to this, I was hoping to push this in a few days. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Compilers and MPI Port Groups
s...@macports.org writes: > Hello all and Happy Boxing Day! > > I have done a complete rewrite of the compilers and mpi port groups > based on suggestions from previous emails. I will try to keep this email > short and provide links for those that want to know more. > > Highlights: > > - specify which compilers to set via compilers.choose, > e.g. 'compilers.choose f77 f90 fc' > > - functions for testing if fortran has been selected for optional > interfaces > > - portfile author can specify if fortran (or mpi) is required > > - unified and have made non-conflicting openmpi and mpich ports; also > added an openmpi-devel port [1] > > - can now select either mpi port as the default mpi installation > > Example of a portfile using the new compilers portgroup: > https://smf.io/macports/changeset/compilers > > Example of a portfile that uses the mpi portgroup: > https://smf.io/macports/files/mpi/dports/science/hdf5-18/Portfile > > The changes I made to the sparskit and hdf5-18 portfiles are just > examples I did for illustrative purposes. I won't push them unless the > portfile author wants it. The mpich and openmpi portfiles need these > changes so that the mpi portgroup will work. > > Anyway, I'd like to push this soon so that I can continue other work > (and close a lot of tickets), so it'd be great if others could take a > look at the proposed changes. > > [1] https://smf.io/macports/changeset/81bb51 or look at the changelog > https://smf.io/macports/changelog to see all the diffs Just an update to say that I've gone ahead and finished updating all the ports that use mpi to use this new port group. The only work that needs to be done is to get some review of this patch series and after that, permission to push. I've cc'd the people who are the maintainers of the ports I changed, listed below. It'd be great to have you guys look at the changes. dstrubbe: sparskit, hpl, octopus eborisch: mpich mww: openmpi raimue: valgrind, valgrind-devel takeshi: berkeley_upc, omnixmp, gnudatalanguage, netcdf, netcdf-cxx, netcdf-cxx4, netcdf-fortran mmoll: optpp, hdf5-18, arpack hum: plda howarth: apbs-mpi mattoates: raxml mk: scotch michaelld: SuiteSparse Check out http://smf.io/macports for the updated changes. Having other people look at this would be great and hopefully would catch some of the errors I missed. The common ones I noticed were missing revbumps (though, I think I got all of those now). Documentation is very much "read the comments and the code itself or look at an example" so, apologies about that. Also, sometimes I couldn't think of a good name for a proc, so if anyone has a better name, please speak up. Some changes since last email are: - ensure the same mpi is used via mpi.enforce_variant - ensure the same c compiler is used (even when using mpi) via compilers.enforce_c - similar for fortran, compilers.enforce_fortran - test for avx compatible compiler via avx_variant_isset Still yet to be done is to replace all custom recipes done for the compiler variants. By my count, there are no more than 72 of those ports. This is lower priority since they'll still work as is. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
