Compiler Wrappers Erroneously in Path for spack setup; breaks things sometimes. #2055
Description
I am following Developing Software with Spack section from documentation and see following error:
$ mkdir build; cd build
$ ../spconfig.py ..
-- The C compiler identification is GNU 4.9.3
-- The CXX compiler identification is GNU 4.9.3
-- Checking whether C compiler has -isysroot
-- Checking whether C compiler has -isysroot - yes
-- Checking whether C compiler supports OSX deployment target flag
-- Checking whether C compiler supports OSX deployment target flag - yes
-- Check for working C compiler: /Users/kumbhar/workarena/software/sources/spack/opt/spack/darwin-elcapitan-x86_64/gcc-4.2.1/gcc-4.9.3-3yghgmzvmbiqmem7lpu2dmcqz6qoqcjd/bin/gcc
-- Check for working C compiler: /Users/kumbhar/workarena/software/sources/spack/opt/spack/darwin-elcapitan-x86_64/gcc-4.2.1/gcc-4.9.3-3yghgmzvmbiqmem7lpu2dmcqz6qoqcjd/bin/gcc -- broken
….
/Users/kumbhar/workarena/software/sources/spack/opt/spack/darwin-elcapitan-x86_64/gcc-4.2.1/gcc-4.9.3-3yghgmzvmbiqmem7lpu2dmcqz6qoqcjd/bin/gcc
-Wl,-search_paths_first -Wl,-headerpad_max_install_names
CMakeFiles/cmTC_afeb5.dir/testCCompiler.c.o -o cmTC_afeb5
Spack compiler must be run from Spack! Input 'SPACK_PREFIX' is
missing.collect2: error: ld returned 1 exit statusIn some other thread (#1111) I came across spack env. Using this I get all environment as:
spack env mylib@develop bash
and then it works fine. Is above the missing step from the workflow document?
I have another question related to extending CMakePackage and spconfig.py:
When I started writing packages for CMake based projects, I have extended packages from Package. Now when I do spack setup my_spec in the source directory of the project, spconfig.py is not generated. But I have install method defined in the package.py with spack-build as build directory. So when I invokespack setup, it build and install the package. And then for development purpose I just do:
cd speck-build
spack env spec_with_spaces - - bash
# change code - make - change code .....which works fine! Is there any drawback of this compared to having spconfig.py?
@citibeth : any suggestion?