1 compiler (called from 2 symbolic links) -> 2 different libtool scripts

[Ethan Mallove]

Hello,

I'm using libtool with the Sun Studio Ceres compilers, and I
see a different resulting libtool script when I configure
with CC=sunCC versus CC=cc (though they both point to the
same executable). The Sun Studio installation has the below
symbolic links:
  
  $ ls -l /opt/SUNWspro/bin/*CC
  lrwxrwxrwx 1 nik staff 14 Jul 11 15:33 /opt/SUNWspro/bin/CC -> ../prod/bin/CC
  lrwxrwxrwx 1 nik staff 14 Jul 11 15:33 /opt/SUNWspro/bin/sunCC -> 
../prod/bin/CC

If I use the "CC" link, all is well. If I use the "sunCC"
link, I get a bad libtool script. E.g.,

Using CC (good archive_cmds):

  # Good archive_cmds
  archive_cmds="\$CC -G\${allow_undefined_flag}  -h\$soname -o \$lib 
\$predep_objects \$libobjs \$deplibs \$postdep_objects \$compiler_flags"
 
Using sunCC (bad archive_cmds):

  archive_cmds=""

Is it possible the libtool macros do things differently
depending on a symlink name?

Based on this -V output, it seems as though the compilers
are aware of the symlink they're called from:

  $ /opt/SUNWspro/bin/sunCC -V
  sunCC: Sun Ceres C++ 5.10 SunOS_sparc 2008/07/10
  ...
  $ /opt/SUNWspro/bin/CC -V
  CC: Sun Ceres C++ 5.10 SunOS_sparc 2008/07/10
  ...

Thanks,
Ethan