This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Richard Biener <richard.guenther@gmail.com> skribis:
On Wed, Feb 13, 2013 at 12:13 PM, Richard Biener <richard.guenther@gmail.com> wrote:On Tue, Feb 12, 2013 at 9:41 PM, Ludovic CourtÃs <ludo@gnu.org> wrote:Joel Sherrill <joel.sherrill@oarcorp.com> skribis:
But it still doesn't address the situation where you have multiple cross compilers in your PATH all for different targets.
Yeah, I thought about it, but couldnât come up with a practical use case where youâd need to use different cross-compilers in a single build.
When you create fat binaries.
That is, a more pragmatic approach would be to not honor these environments in a cross compiler at all.
Possibly, though thatâd be an incompatible change.I am having difficulties to imagine such a need.
At any rate, thereâs a need for similar env. vars for cross-compilers. WDYT?
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |