@@ -123,21 +123,21 @@ that the packages is installed:
123123
124124 $ spack install mpileaks
125125 ==> Installing mpileaks
126- ==> mpich is already installed in /home/gamblin2 /spack/opt/linux-debian7-x86_64/gcc@4.4.7/mpich@3.0.4.
127- ==> callpath is already installed in /home/gamblin2 /spack/opt/linux-debian7-x86_64/gcc@4.4.7/callpath@1.0.2-5dce4318.
128- ==> adept-utils is already installed in /home/gamblin2 /spack/opt/linux-debian7-x86_64/gcc@4.4.7/adept-utils@1.0-5adef8da.
126+ ==> mpich is already installed in ~ /spack/opt/linux-debian7-x86_64/gcc@4.4.7/mpich@3.0.4.
127+ ==> callpath is already installed in ~ /spack/opt/linux-debian7-x86_64/gcc@4.4.7/callpath@1.0.2-5dce4318.
128+ ==> adept-utils is already installed in ~ /spack/opt/linux-debian7-x86_64/gcc@4.4.7/adept-utils@1.0-5adef8da.
129129 ==> Trying to fetch from https://github.com/hpc/mpileaks/releases/download/v1.0/mpileaks-1.0.tar.gz
130130 ######################################################################## 100.0%
131- ==> Staging archive: /home/gamblin2 /spack/var/spack/stage/mpileaks@1.0%gcc@4.4.7 arch=linux-debian7-x86_64-59f6ad23/mpileaks-1.0.tar.gz
132- ==> Created stage in /home/gamblin2 /spack/var/spack/stage/mpileaks@1.0%gcc@4.4.7 arch=linux-debian7-x86_64-59f6ad23.
131+ ==> Staging archive: ~ /spack/var/spack/stage/mpileaks@1.0%gcc@4.4.7 arch=linux-debian7-x86_64-59f6ad23/mpileaks-1.0.tar.gz
132+ ==> Created stage in ~ /spack/var/spack/stage/mpileaks@1.0%gcc@4.4.7 arch=linux-debian7-x86_64-59f6ad23.
133133 ==> No patches needed for mpileaks.
134134 ==> Building mpileaks.
135135
136136 ... build output ...
137137
138138 ==> Successfully installed mpileaks.
139139 Fetch: 2.16s. Build: 9.82s. Total: 11.98s.
140- [+] /home/gamblin2 /spack/opt/linux-debian7-x86_64/gcc@4.4.7/mpileaks@1.0-59f6ad23
140+ [+] ~ /spack/opt/linux-debian7-x86_64/gcc@4.4.7/mpileaks@1.0-59f6ad23
141141
142142 The last line, with the ``[+] ``, indicates where the package is
143143installed.
@@ -252,7 +252,7 @@ the tarballs in question to it (see :ref:`mirrors`):
252252 .. code-block :: yaml
253253
254254 mirrors :
255- manual : file:///home/me /.spack/manual_mirror
255+ manual : file://~ /.spack/manual_mirror
256256
257257 #. Put your tarballs in it. Tarballs should be named
258258 ``<package>/<package>-<version>.tar.gz ``. For example:
@@ -374,13 +374,13 @@ use ``spack find --paths``:
374374 $ spack find --paths
375375 ==> 74 installed packages.
376376 -- linux-debian7-x86_64 / gcc@4.4.7 --------------------------------
377- ImageMagick@6.8.9-10 /home/gamblin2 /spack/opt/linux-debian7-x86_64/gcc@4.4.7/ImageMagick@6.8.9-10-4df950dd
378- adept-utils@1.0 /home/gamblin2 /spack/opt/linux-debian7-x86_64/gcc@4.4.7/adept-utils@1.0-5adef8da
379- atk@2.14.0 /home/gamblin2 /spack/opt/linux-debian7-x86_64/gcc@4.4.7/atk@2.14.0-3d09ac09
380- boost@1.55.0 /home/gamblin2 /spack/opt/linux-debian7-x86_64/gcc@4.4.7/boost@1.55.0
381- bzip2@1.0.6 /home/gamblin2 /spack/opt/linux-debian7-x86_64/gcc@4.4.7/bzip2@1.0.6
382- cairo@1.14.0 /home/gamblin2 /spack/opt/linux-debian7-x86_64/gcc@4.4.7/cairo@1.14.0-fcc2ab44
383- callpath@1.0.2 /home/gamblin2 /spack/opt/linux-debian7-x86_64/gcc@4.4.7/callpath@1.0.2-5dce4318
377+ ImageMagick@6.8.9-10 ~ /spack/opt/linux-debian7-x86_64/gcc@4.4.7/ImageMagick@6.8.9-10-4df950dd
378+ adept-utils@1.0 ~ /spack/opt/linux-debian7-x86_64/gcc@4.4.7/adept-utils@1.0-5adef8da
379+ atk@2.14.0 ~ /spack/opt/linux-debian7-x86_64/gcc@4.4.7/atk@2.14.0-3d09ac09
380+ boost@1.55.0 ~ /spack/opt/linux-debian7-x86_64/gcc@4.4.7/boost@1.55.0
381+ bzip2@1.0.6 ~ /spack/opt/linux-debian7-x86_64/gcc@4.4.7/bzip2@1.0.6
382+ cairo@1.14.0 ~ /spack/opt/linux-debian7-x86_64/gcc@4.4.7/cairo@1.14.0-fcc2ab44
383+ callpath@1.0.2 ~ /spack/opt/linux-debian7-x86_64/gcc@4.4.7/callpath@1.0.2-5dce4318
384384 ...
385385
386386 And, finally, you can restrict your search to a particular package
@@ -390,9 +390,9 @@ by supplying its name:
390390
391391 $ spack find --paths libelf
392392 -- linux-debian7-x86_64 / gcc@4.4.7 --------------------------------
393- libelf@0.8.11 /home/gamblin2 /spack/opt/linux-debian7-x86_64/gcc@4.4.7/libelf@0.8.11
394- libelf@0.8.12 /home/gamblin2 /spack/opt/linux-debian7-x86_64/gcc@4.4.7/libelf@0.8.12
395- libelf@0.8.13 /home/gamblin2 /spack/opt/linux-debian7-x86_64/gcc@4.4.7/libelf@0.8.13
393+ libelf@0.8.11 ~ /spack/opt/linux-debian7-x86_64/gcc@4.4.7/libelf@0.8.11
394+ libelf@0.8.12 ~ /spack/opt/linux-debian7-x86_64/gcc@4.4.7/libelf@0.8.12
395+ libelf@0.8.13 ~ /spack/opt/linux-debian7-x86_64/gcc@4.4.7/libelf@0.8.13
396396
397397 ``spack find `` actually does a lot more than this. You can use
398398*specs * to query for specific configurations and builds of each
@@ -647,8 +647,8 @@ avoid ambiguity.
647647
648648When spack normalizes specs, it prints them out with no spaces boolean
649649variants using the backwards compatibility syntax and uses only ``~ ``
650- for disabled boolean variants. We allow ``- `` and spaces on the command
651- line is provided for convenience and legibility.
650+ for disabled boolean variants. The ``- `` and spaces on the command
651+ line are provided for convenience and legibility.
652652
653653^^^^^^^^^^^^^^
654654Compiler Flags
@@ -658,14 +658,17 @@ Compiler flags are specified using the same syntax as non-boolean variants,
658658but fulfill a different purpose. While the function of a variant is set by
659659the package, compiler flags are used by the compiler wrappers to inject
660660flags into the compile line of the build. Additionally, compiler flags are
661- inherited by dependencies. ``spack install libdwarf cppflags=\ "-g\ " `` will
661+ inherited by dependencies. ``spack install libdwarf cppflags="-g" `` will
662662install both libdwarf and libelf with the ``-g `` flag injected into their
663663compile line.
664664
665- Notice that the value of the compiler flags must be escape quoted on the
666- command line. From within python files, the same spec would be specified
667- ``libdwarf cppflags="-g" ``. This is necessary because of how the shell
668- handles the quote symbols.
665+ Notice that the value of the compiler flags must be quoted if it
666+ contains any spaces. Any of ``cppflags=-O3 ``, ``cppflags="-O3" ``,
667+ ``cppflags='-O3' ``, and ``cppflags="-O3 -fPIC" `` are acceptable, but
668+ ``cppflags=-O3 -fPIC `` is not. Additionally, if they value of the
669+ compiler flags is not the last thing on the line, it must be followed
670+ by a space. The commmand ``spack install libelf cppflags="-O3"%intel ``
671+ will be interpreted as an attempt to set `cppflags="-O3%intel"``.
669672
670673The six compiler flags are injected in the order of implicit make commands
671674in GNU Autotools. If all flags are set, the order is
@@ -900,7 +903,7 @@ prefixes, and you can see this with ``spack find --paths``:
900903 $ spack find --paths py-numpy
901904 ==> 1 installed packages.
902905 -- linux-debian7-x86_64 / gcc@4.4.7 --------------------------------
903- py-numpy@1.9.1 /g/g21/gamblin2/src /spack/opt/linux-debian7-x86_64/gcc@4.4.7/py-numpy@1.9.1-66733244
906+ py-numpy@1.9.1 ~ /spack/opt/linux-debian7-x86_64/gcc@4.4.7/py-numpy@1.9.1-66733244
904907
905908 However, even though this package is installed, you cannot use it
906909directly when you run ``python ``:
0 commit comments