ts: improve coverage of Tcl ext library on OSX
Test Modules Tcl extended C library on Mac OSX against broken syscall that are injected through DYLD, using its interposing mechanism [1].
[1] http://toves.freeshell.org/interpose/
Signed-off-by: Xavier Delaruelle xavier.delaruelle@cea.fr
版权所有:中国计算机学会技术支持:开源发展技术委员会
京ICP备13000930号-9
京公网安备 11010802047560号
Modules, provides dynamic modification of a user’s environment
The Modules package is a tool that simplify shell initialization and lets users easily modify their environment during the session with modulefiles.
Each modulefile contains the information needed to configure the shell for an application. Once the Modules package is initialized, the environment can be modified on a per-module basis using the module command which interprets modulefiles. Typically modulefiles instruct the module command to alter or set shell environment variables such as PATH, MANPATH, etc. modulefiles may be shared by many users on a system and users may have their own collection to supplement or replace the shared modulefiles.
Modules can be loaded and unloaded dynamically and atomically, in an clean fashion. All popular shells are supported, including bash, ksh, zsh, sh, csh, tcsh, fish, cmd, pwsh, as well as some scripting languages such as tcl, perl, python, ruby, cmake and r.
Modules are useful in managing different versions of applications. Modules can also be bundled into meta-modules that will load an entire suite of different applications.
Quick examples
Here is an example of loading a module on a Linux machine under bash.
Now we’ll switch to a different version of the module
And now we’ll unload the module altogether
Now we’ll log into a different machine, using a different shell (tcsh).
Note that the command line is exactly the same, but the path has automatically configured to the correct architecture.
Getting things running
The simplest way to build and install Modules on a Unix system is:
To learn the details on how to install modules see
INSTALL.txtfor Unix system orINSTALL-win.txtfor Windows.Requirements
Documentation
See
MIGRATINGto get an overlook of the new functionalities introduced by each released versions.NEWSprovides the full list of changes added in each version. TheChangesdocument gives an in-depth view of the modified behaviors and new features between major versions. You may also look at theChangeLogfor the technical development details.The
docdirectory contains both the paper and man pages describing the user’s and the module writer’s usage. To generate the documentation files, like the man pages (you need Sphinx >= 1.0 to build the documentation), just type:The following man pages are provided:
Test suite
Regression testing scripts are available in the
testsuitedirectory (you need DejaGnu to run the test suite):Once modules is installed after running
make install, you have the ability to test this installation with:Links
Community
Modules is an open source project. Questions, discussion, and contributions are welcome. You can get in contact with the Modules community via:
modules-interest@lists.hpsf.io)#modules:matrix.org)The project is also present on several social media platforms:
Contributing
Modules project welcomes contributions of all kinds! Before submitting an issue or pull request, please take a moment to review our Contributing guide. It includes important information about issue reporting, coding standards, etc.
Please note that Modules project has a Code of conduct. It ensures a respectful and inclusive environment for all contributors. By participating in the Modules community, you agree to abide by its rules.
Governance
Modules is part of the High Performance Software Foundation within the Linux Foundation.
This project adheres to a Technical charter, which defines its governance model, decision-making process, and long-term vision.
License
Modules is distributed under the GNU General Public License, either version 2 or (at your option) any later version (
GPL-2.0-or-later). Read the fileCOPYING.GPLv2for details.Authors
Modules current maintainers are:
Many thanks go to the contributors of the Modules project.
Acknowledgments
We would like to express our gratitude to CEA for the resources and funding provided to the project over the recent years.
The following people have notably contributed to Modules and Modules would not be what it is without their contributions: