Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
Spack
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
eic_tools
Spack
Commits
3895c974
Commit
3895c974
authored
8 years ago
by
Elizabeth Fischer
Committed by
Todd Gamblin
8 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Removed documentation on false paths as per #2083 (#2146)
Removed documentation on false paths as per #2083
parent
9f54cea5
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
lib/spack/docs/configuration.rst
+0
-28
0 additions, 28 deletions
lib/spack/docs/configuration.rst
lib/spack/docs/getting_started.rst
+1
-12
1 addition, 12 deletions
lib/spack/docs/getting_started.rst
with
1 addition
and
40 deletions
lib/spack/docs/configuration.rst
+
0
−
28
View file @
3895c974
...
@@ -134,34 +134,6 @@ buggy or otherwise undesirable.
...
@@ -134,34 +134,6 @@ buggy or otherwise undesirable.
.. _system-packages:
.. _system-packages:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
False Paths for System Packages
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Sometimes, the externally-installed package one wishes to use with
Spack comes with the Operating System and is installed in a standard
place --- ``/usr``, for example. Many other packages are there as
well. If Spack adds it to build paths, then some packages might
pick up dependencies from ``/usr`` than the intended Spack version.
In order to avoid this problem, it is advisable to specify a fake path
in ``packages.yaml``, thereby preventing Spack from adding the real
path to compiler command lines. This will work because compilers
normally search standard system paths, even if they are not on the
command line. For example:
.. code-block:: yaml
packages:
# Recommended for security reasons
# Do not install OpenSSL as non-root user.
openssl:
paths:
openssl@system: /false/path
version: [system]
buildable: False
^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^
Extracting System Packages
Extracting System Packages
^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^
...
...
This diff is collapsed.
Click to expand it.
lib/spack/docs/getting_started.rst
+
1
−
12
View file @
3895c974
...
@@ -730,21 +730,10 @@ there." This is reasonable for OpenSSL, which has a stable API.
...
@@ -730,21 +730,10 @@ there." This is reasonable for OpenSSL, which has a stable API.
packages:
packages:
openssl:
openssl:
paths:
paths:
openssl@system: /
false/path
openssl@system: /
usr
version: [system]
version: [system]
buildable: False
buildable: False
.. note::
Even though OpenSSL is located in ``/usr``, We have told Spack to
look for it in ``/false/path``. This prevents ``/usr`` from being
added to compilation paths and RPATHs, where it could cause
unrelated system libraries to be used instead of their Spack
equivalents.
The adding of ``/usr`` to ``RPATH`` in this sitution is a known issue
and will be fixed in a future release.
^^^^^^^^^^^^^
^^^^^^^^^^^^^
BLAS / LAPACK
BLAS / LAPACK
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment