Make all gets the same environment as make install (assuming you do it in the same shell). But if you sudo make install, the environment may be different - it may not inherit everything from your environment.
I advised the user to "sudo -s" and ten setup the compiler environment and then run make install.
Sent from my phone. No type good.
On May 7, 2011, at 9:37 PM, "Dmitry N. Mikushin" <maemarcus_at_[hidden]> wrote:
> I certainly do not expect anything special, just normally "make
> install" should not have issues, if "make" passes fine, right? What we
> have with OpenMPI is this strange difference: if ./configure CC=icc,
> "make" works, and "make install" - does not; if ./configure
> CC=/full/path/to/icc, then both "make" and "make install" work.
> Nothing needs to be searched, icc is already in PATH, since
> compilevars are sourced in profile.d. Or am I missing something?
> - D.
> 2011/5/8 Tim Prince <n8tm_at_[hidden]>:
>> On 5/7/2011 2:35 PM, Dmitry N. Mikushin wrote:
>>>> didn't find the icc compiler
>>> Jeff, on 1.4.3 I saw the same issue, even more generally: "make
>>> install" cannot find the compiler, if it is an alien compiler (i.e.
>>> not the default gcc) - same situation for intel or llvm, for example.
>>> The workaround is to specify full paths to compilers with CC=...
>>> FC=... in ./configure params. Could it be "make install" breaks some
>>> env paths?
>> Most likely reason for not finding an installed icc is that the icc
>> environment (source the compilervars script if you have a current version)
>> wasn't set prior to running configure. Setting up the compiler in question
>> in accordance with its own instructions is a more likely solution than the
>> absolute path choice.
>> OpenMPI configure, for good reason, doesn't search your system to see where
>> a compiler might be installed. What if you had 2 versions of the same named
>> Tim Prince
>> users mailing list
> users mailing list