text stringclasses 683
values |
|---|
Copyright: |
numactl and the demo programs are under the GNU General Public License, v.2 |
libnuma is under the GNU Lesser General Public License, v2.1. |
The manpages are under the same license as the Linux manpages (see the files) |
numademo links with a library derived from the C version of STREAM |
by John D. McCalpin and Joe R. Zagar for one sub benchmark. See stream_lib.c |
for the license. In particular when you publish numademo output |
you might need to pay attention there or filter out the STREAM results. |
It also uses a public domain Mersenne Twister implementation from |
Michael Brundage. |
GNU GENERAL PUBLIC LICENSE |
Version 2, June 1991 |
Copyright (C) 1989, 1991 Free Software Foundation, Inc., |
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA |
Everyone is permitted to copy and distribute verbatim copies |
of this license document, but changing it is not allowed. |
Preamble |
The licenses for most software are designed to take away your |
freedom to share and change it. By contrast, the GNU General Public |
License is intended to guarantee your freedom to share and change free |
software--to make sure the software is free for all its users. This |
General Public License applies to most of the Free Software |
Foundation's software and to any other program whose authors commit to |
using it. (Some other Free Software Foundation software is covered by |
the GNU Lesser General Public License instead.) You can apply it to |
your programs, too. |
When we speak of free software, we are referring to freedom, not |
price. Our General Public Licenses are designed to make sure that you |
have the freedom to distribute copies of free software (and charge for |
this service if you wish), that you receive source code or can get it |
if you want it, that you can change the software or use pieces of it |
in new free programs; and that you know you can do these things. |
To protect your rights, we need to make restrictions that forbid |
anyone to deny you these rights or to ask you to surrender the rights. |
These restrictions translate to certain responsibilities for you if you |
distribute copies of the software, or if you modify it. |
For example, if you distribute copies of such a program, whether |
gratis or for a fee, you must give the recipients all the rights that |
you have. You must make sure that they, too, receive or can get the |
source code. And you must show them these terms so they know their |
rights. |
We protect your rights with two steps: (1) copyright the software, and |
(2) offer you this license which gives you legal permission to copy, |
distribute and/or modify the software. |
Also, for each author's protection and ours, we want to make certain |
that everyone understands that there is no warranty for this free |
software. If the software is modified by someone else and passed on, we |
want its recipients to know that what they have is not the original, so |
that any problems introduced by others will not reflect on the original |
authors' reputations. |
Finally, any free program is threatened constantly by software |
patents. We wish to avoid the danger that redistributors of a free |
program will individually obtain patent licenses, in effect making the |
program proprietary. To prevent this, we have made it clear that any |
patent must be licensed for everyone's free use or not licensed at all. |
The precise terms and conditions for copying, distribution and |
modification follow. |
GNU GENERAL PUBLIC LICENSE |
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION |
0. This License applies to any program or other work which contains |
a notice placed by the copyright holder saying it may be distributed |
under the terms of this General Public License. The "Program", below, |
refers to any such program or work, and a "work based on the Program" |
means either the Program or any derivative work under copyright law: |
that is to say, a work containing the Program or a portion of it, |
either verbatim or with modifications and/or translated into another |
language. (Hereinafter, translation is included without limitation in |
the term "modification".) Each licensee is addressed as "you". |
Activities other than copying, distribution and modification are not |
covered by this License; they are outside its scope. The act of |
running the Program is not restricted, and the output from the Program |
is covered only if its contents constitute a work based on the |
Program (independent of having been made by running the Program). |
Whether that is true depends on what the Program does. |
1. You may copy and distribute verbatim copies of the Program's |
source code as you receive it, in any medium, provided that you |
conspicuously and appropriately publish on each copy an appropriate |
copyright notice and disclaimer of warranty; keep intact all the |
notices that refer to this License and to the absence of any warranty; |
and give any other recipients of the Program a copy of this License |
along with the Program. |
End of preview. Expand in Data Studio
YAML Metadata Warning:empty or missing yaml metadata in repo card
Check out the documentation for more information.
cdt-builds
conda-forge Core Dependency Tree (CDT) builds
cdt_slugs.yaml Configuration Options
The following options are available when adding a CDT in the configuration file:
custom(boolean): Set totrueto declare the CDT as a custom CDT. This will cause the CDT generation code to remove any instance of the CDT that appears in thecdtsorlegacy_cdtsdirectories.license_file(str or list of str or null): Sets the license file for a CDT. If set to a string or a list of strings giving the paths to the files, it will copy the licenses to the recipe and modify the recipemeta.yamlappropriately. If set tonull, it will remove thelicense_filekey from themeta.yaml.skipped_cdts(list of str): Set to a list of the distribution and platforms to skip for this CDT. For example, one might addcos6-x86_64to this list to skip making this CDT for CentOS 6 onx86_64architectures.build_append(dict mapping dist-arch to a string): Set this key to append code to thebuild.shfile for a given distribution and platform. For example, one might set a keycos6-x86_64in this mapping and set the value toecho 'hi!'to addecho 'hi!'to the build script for onlycos6-x86_64.dep_remove(list of strings): Set to a list of strings for deps that should be removedep_replace(dict mapping dep to replace to new dep): Set to a dict of deps to be replaced by another dep. this can be used for aliased RPMs.
Adding a CDT package
To add a CDT package, make a PR on this repo with the following changes.
- Add the name of the CDT
cdt_slugs.yamlfile. - Run the python script
gen_cdt_recipes.py. This script will generate the CDT recipes that do not exist. Pass--forceto regenerate all of the CDT recipes (takes about 10-20 minutes to complete). - Commit any changes from steps 1+2 and open the PR.
The CI service will build the CDTs, report any errors, etc.
Changing the CDT generation script rpm.py
If you make changes to the CDT generation script, make a PR on this repo using the following steps.
- Make sure the bump the
cdt_build_numbervariable in theconda_build_config.yamlfile. - Run the python script
gen_cdt_recipes.py. This script will generate the CDT recipes that do not exist. Pass--forceto regenerate all of the CDT recipes (takes about 10-20 minutes to complete). - Commit any changes from steps 1+2 and open the PR.
The CI service will build the CDTs, report any errors, etc.
Making Custom CDT recipes
If you have a CDT recipe that is not autogenerated, it can be added as follows.
- Add the CDT name to the
cdt_slugs.yamlfile. Make sure to setcustom: truein the metadata in the file. - Add the CDT recipe in a directory under the full CDT package name in either
the
custom_cdtsorlegacy_custom_cdtsfolder depending on whether or not the CDT is targeted at the old-style CDT format or the new-style one. If you do not know, ask someone onconda-forge/core. - Commit any changes from steps 1+2 and open the PR.
The CI service will build the CDTs, report any errors, etc.
Old-style/legacy vs. New-style CDTs
The old-style CDTs are targeted at the conda-forge compilers that do not use the
sysroot_{conda subdir} packages (e.g., sysroot_linux-64, sysroot_linux-aarch64, etc.)
and build their own copy of glibc. These compilers also have cos6 or cos7
in the name of the sysroot directory. The new-style CDTs use a sysroot directory
without cos6 or cos7 and are meant to work with the new conda-forge
compilers that depend on the sysroot_{conda subdir} packages.
old-style CDT specs
- needs to have
no_hoistin the source sections - sysroot directory has
conda_cos6orconda_cos7in the path - needs to have
run_constrainedentry ofsysroot_{conda subdir} ==99999999999to prevent it from being co-installed w/ the new compilers or CDTs
new-style CDT specs
- needs to have
no_hoistin the source sections - sysroot directory has
condaonly in the path - needs to have a
runrequirement on the proper version of thesysroot_{subdir}package so that it is only installed with CDTs from the right version of CentOS - the versions of
sysroot_{conda subdir}are 2.12 for CentOS 6 and 2.17 for CentOS 7.
Azure CI Setup
This bit of code was run to setup azure.
from conda_smithy.azure_ci_utils import register_repo, AzureConfig
cfg = AzureConfig(project_name='cdt-builds')
register_repo("conda-forge", "cdt-builds", config=cfg)
Current CDT Builds
- Downloads last month
- 135