[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Regarding my two patches against config.sub
|
From: |
Jan Engelhardt |
|
Subject: |
Re: Regarding my two patches against config.sub |
|
Date: |
Sat, 2 Feb 2013 07:38:28 +0100 (CET) |
|
User-agent: |
Alpine 2.01 (LNX 1266 2009-07-14) |
On Friday 2013-02-01 16:23, Yann Droneaud wrote:
>
>The rationale behind this is:
>
>when using ./configure --host=<name>, --build=<name>,--target=<name>,
><name> is not the output of config.guess and can be written in
>upper-case. For example ./configure --host=X86-LINUX
But the question is: why would anybody want to write X86-LINUX
instead of x86-linux?
- Regarding my two patches against config.sub, Yann Droneaud, 2013/02/01
- Re: Regarding my two patches against config.sub,
Jan Engelhardt <=
- Re: Regarding my two patches against config.sub, Yann Droneaud, 2013/02/02
- Re: Regarding my two patches against config.sub, Ben Elliston, 2013/02/02
- Re: Regarding my two patches against config.sub, Yann Droneaud, 2013/02/02
- Re: Regarding my two patches against config.sub, Ben Elliston, 2013/02/02
- Message not available
- Need for --build with --host when cross-compiling ?, Yann Droneaud, 2013/02/03
- Re: Need for --build with --host when cross-compiling ?, Jan Engelhardt, 2013/02/05
- Re: Need for --build with --host when cross-compiling ?, Yann Droneaud, 2013/02/12
- Re: Need for --build with --host when cross-compiling ?, Jan Engelhardt, 2013/02/12
- Message not available
- Uppercase in cross-compiler name, Yann Droneaud, 2013/02/03
Re: Regarding my two patches against config.sub, Ben Elliston, 2013/02/02