Re: [RFA] Use full path for system compiler, not just the first word.

[Robert Boehne]

Klee,

I think you can get the desired effect by setting CC, CXX, F77, etc. to
the full path + options that you want to use for your compiler.
example:
  ./configure --enable-blah --disable-foo CC="cc -64" CXX="CC -64
-LANG:std"

It is normal practice to use CFLAGS to pass compiler flags anyway.
If these solutions don't work please let us know.

Thanks,

Robert Boehne


Klee Dienes wrote:
> 
> When building the gcc source tree, gcc passes down a rather convoluted
> compile-command for use by sub-makes to build libraries for the target
> using the just-built gcc.  Unfortunately, libtool strips off all but
> the first word of the command, and tries to use the result as a
> compiler-driver, which doesn't always work (since it's missing -B
> options and etc.).  The following patch changes libtool to use the full
> compile-command as the compiler driver (while still correctly setting
> cc_basename):
> 
>   ------------------------------------------------------------------------
>                         Name: libtool-diffs.txt
>    libtool-diffs.txt    Type: Plain Text (text/plain)
>                     Encoding: 7bit
> 
>   ------------------------------------------------------------------------
> 
>   ------------------------------------------------------------------------
> _______________________________________________
> Libtool-patches mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/libtool-patches