Re: another 1.5 release?

[Alexandre Oliva]

On Jan 30, 2005, Daniel Reed <address@hidden> wrote:

> With a tag specified, Libtool accepts a different linker but still uses its
> internal library searching routines (which would use the multilib2 path),

But wouldn't it use the $CC built into it at configure time, as
opposed to the one specified at link time?

Still, changing the compiler is, and has never been, supported.  The
very point of configuring the compiler and detecting its properties at
configure time is to enable the use of options that are specific to
the compiler without having to do the detection at every use.

Switching from gcc 3.4 to gcc 4 is probably always going to work.
Switching from say gcc to a platform-specific vendor-supplied
proprietary compiler probably won't.

-- 
Alexandre Oliva             http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer   address@hidden, gcc.gnu.org}
Free Software Evangelist  address@hidden, gnu.org}