[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: If -xarch passed in, don't set compiler_flags _only_ for GCC
From: |
Ralf Wildenhues |
Subject: |
Re: If -xarch passed in, don't set compiler_flags _only_ for GCC |
Date: |
Tue, 18 Oct 2005 09:32:56 +0200 |
User-agent: |
Mutt/1.5.11 |
Hi Albert, Keith, Donald,
* Albert Chin wrote on Mon, Oct 17, 2005 at 11:07:04PM CEST:
> HEAD sets compiler_flags in the code below regardless of whether or
> not GCC is the compiler. Why does branch-1-5 do it differently? If
> someone is building a 64-bit library with the Sun C++ compiler,
> -xarch=v9 won't get passed through and ld will try to create a 32-bit
> library, resulting in an error.
Thanks for the patch. Applied to branch-1-5.
Cheers,
Ralf
> 2005-10-17 Albert Chin-A-Young <address@hidden>
>
> * ltmain.in: When accepting -64, -mips[0-9], et. al. compiler
> flags, don't set compiler_flags only for GCC as the vendor
> compiler also requires this flag. Sync with HEAD.
> Reported by Donald Anderson <address@hidden>.