In Modules/ld_so_aix there is `which $CC` to search for the full compiler's path.

Unfortunately, /usr/bin/which on AIX is a csh-script and thus ~/.cshrc gets sourced before doing the path search.

Now, when the user does set some PATH in ~/.cshrc, `which` might print a wrong path for the compiler, causing the build to fail (at best).

It would be better to do the path search without launching an external program.

Uhm, as I read the patch again, there's room for improvement of pywhich():
it likely fails with CC=/full/path/to/cc

@Michael: do you intend putting in a new patch for review as hinted at in msg98071?

I'm not sure this should be changed:

  1) Why is .cshrc sourced? It should only get sourced for a login
     shell.

  2) If the user sets a PATH that excludes the compiler, then `which`
     will also not find the compiler on other systems (like Linux).
     Why would anyone set a PATH that excludes the compiler?


Sridhar, has this ever been a problem for you on AIX?

On 2010-07-22, at 11:56 AM, Stefan Krah wrote:

> 
> Stefan Krah <stefan-usenet@bytereef.org> added the comment:
> 
> I'm not sure this should be changed:
> 
>  1) Why is .cshrc sourced? It should only get sourced for a login
>     shell.

/usr/bin/which is a csh script on our AIX machine too:

bash-2.04$ head -n 5 /usr/bin/which
#!/usr/bin/csh -f
set prompt = "% "
if ( -f ~/.cshrc) then
        source ~/.cshrc
endif

>  2) If the user sets a PATH that excludes the compiler, then `which`
>     will also not find the compiler on other systems (like Linux).
>     Why would anyone set a PATH that excludes the compiler?
> 
> 
> Sridhar, has this ever been a problem for you on AIX?

Not at all, we use bash as the default shell.