Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Compiler Wrappers Erroneously in Path for `spack setup`; breaks things sometimes. #2055
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 status
In some other thread (#1111) I came across
and then it works fine. Is above the missing step from the workflow document?
I have another question related to extending
When I started writing packages for CMake based projects, I have extended packages from
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
@citibeth : any suggestion?
A bit of background... for a variety of reasons, Spack wraps your compiler in shell-script wrappers, designed to be run only from within Spack. The
It looks like the
That said... I was not aware of the possibilities you brought up, thank you for mentioning them!
Good news, I ran into this problem too. But only on SOME computers... I don't yet know why some but not all. Anyway... look in the generated
The compiler wrappers are found in the following locations:
These come BEFORE the real compiler, which is found at:
The long-term solution? I could certainly add some code to make sure those three lines don't make it into
OK, I don't know why it's not working. Later on in
On the computer where it does work, these lines seem to be causing CMake to pick up the real compiler, not the Spack wrappers. The
changed the title from
Development workflow : spack setup need spack env ?
Compiler Wrappers Erroneously in Path for `spack setup`; breaks things sometimes.
Oct 23, 2016
Thanks @citibeth for detailed information! I don't have my dev environment setup at the moment, will provide my configurations soon.
Here are some additional points:
referenced this issue
Oct 24, 2016
I think I found the problem, don't think we need additional details.
On Sun, Oct 23, 2016 at 9:48 AM, Pramod Kumbhar email@example.com