On Jan 14 2014, at 01:34 , Erik Joelsson wrote:
> If my memory serves me right, I believe we were uncertain if symlink
> resolving was really the way to go and finally decided to do it because a set
> configuration should not easily be changed without configure being rerun.
>
> Example: If a
On 2014-01-14 10:34, Erik Joelsson wrote:
If my memory serves me right, I believe we were uncertain if symlink
resolving was really the way to go and finally decided to do it
because a set configuration should not easily be changed without
configure being rerun.
Example: If a configuration fi
If my memory serves me right, I believe we were uncertain if symlink
resolving was really the way to go and finally decided to do it because
a set configuration should not easily be changed without configure being
rerun.
Example: If a configuration finds compiler /path/to/A which is actually
On 2014-01-14 02:46, Mike Duigou wrote:
Hello all;
This is a very small change. Currently when TOOLCHAIN_FIND_COMPILER evaluates a compiler
it resolves any symbolic links. This behaviour thwarts compiler setups that use a single
executable and multiple symbolic links that "curry" configuration
Hello all;
This is a very small change. Currently when TOOLCHAIN_FIND_COMPILER evaluates a
compiler it resolves any symbolic links. This behaviour thwarts compiler setups
that use a single executable and multiple symbolic links that "curry"
configuration information into the link name.
http://
