Chapel developers -- Please note that if you are using GASNet communication with Chapel, this will cause a rebuild of the third-party/gasnet package because it changes the build and install subdirectory path for that package. (Not the content, just the so-called unique configuration path.)
greg > On Nov 13, 2017, at 5:55 PM, gbtitus <[email protected]> wrote: > > Branch: refs/heads/master > Revision: a62c1b2 > Author: gbtitus > > Log Message: > ------------ > Merge pull request #7758 from gbtitus/substrate-in-gasnet-uniq-cfg-path > > Include the substrate setting in the gasnet unique config path. > > (Reviewed by @ronawho.) > > The substrate is part of the build-time configuration of GASNet. > Include that setting in our unique config path, so that users can > maintain side-by-side GASNet builds with different substrates and > everything else the same. > > This resolves #7733. > > Modified Files: > --------------- > M third-party/gasnet/Makefile.include > > Compare: > https://github.com/chapel-lang/chapel/compare/13c4f692f7db...a62c1b239aec > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! > http://sdm.link/slashdot_______________________________________________ > Chapel-commits mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/chapel-commits ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
