OK to commit? Ian, do you think this is right?
Akim
Index: ChangeLog
===
RCS file: /cvs/autoconf/ChangeLog,v
retrieving revision 1.564
diff -u -r1.564 ChangeLog
--- ChangeLog 2000/04/28 09:46:55 1.564
+++ ChangeLog
I tested out this patch and it seems to be working just fine for me.
Here is the output I get.
% ~/project/mod_jikes/jikes/src/configure --prefix=/tmp/jikes \
--host=i386-mingw32msvc
checking build system type... i686-pc-linux-gnu
checking host system type... i386-pc-mingw32msvc
checking for c++.
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> On Apr 27, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
>> Should an arg to configure be considered as a --build.
Akim::Alexandre> Yes, so that existing scripts can still run without
Akim::Alexandre> modification.
Ale
On Apr 27, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
> Should an arg to configure be considered as a --build.
Alexandre> Yes, so that existing scripts can still run without
Alexandre> modification.
Not really. An arg to configure should be considered as the default
for --build, --
From: Akim Demaille <[EMAIL PROTECTED]>
Date: 27 Apr 2000 14:14:35 +0200
So now I think we can clearly state the question:
Should an arg to configure be considered as a --build.
I would vote no. I agree that this is not as bad as making a
configure argument be treated as -
From: Alexandre Oliva <[EMAIL PROTECTED]>
Date: 27 Apr 2000 01:06:14 -0300
On Apr 26, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
Alexandre> I don't see any reason to do it. I'd rather keep both
Alexandre> `--host=TRIPLET' and plain `TRIPLET'.
> The fact is that the two sc
Pavoin pavoin!
> "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes:
Pavel> Also look at this: $ ./configure a b configure: error: can only
Pavel> configure for one host and one target at a time
Pavel> "build" is not mentioned.
Yes, but that's correct when you take a look at the clumsy ru
Hello, Akim!
> So now I think we can clearly state the question:
>
> Should an arg to configure be considered as a --build.
Since "configure --help" used to print
Usage: ./configure [OPTION]... [VAR=VALUE]... [HOST]
we should not change [HOST] to [BUILD] without concerns about backwar
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
>> Are you sure that's what the rule was?
Alexandre> That's what AC_CANONICAL_THING does. I didn't look at the
Alexandre> rules. But now that I read them, I see they're exactly
Alexandre> what's implemented, except that I didn't
On Apr 27, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> You mean, because now they'd be considered to be cross
Alexandre> compiling? Hmm... I think I begin to understand why the
Alexandre> current implementation is a
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
>> And are you sure their authors will be happy to see their script
>> still working, but doing something different?
Alexandre> Why would they be doing something different?
I don't know too well, and I confess and don't want to :)
On Apr 27, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
> Hm, what scripts are you thinking about?
Scripts that would run configure and install software, for example.
> And are you sure their authors will be happy to see their script
> still working, but doing something different?
Why would
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> On Apr 26, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote: I
Alexandre> don't see any reason to do it. I'd rather keep both
Alexandre> `--host=TRIPLET' and plain `TRIPLET'.
>> The fact is that the two schemes were not eq
On Apr 26, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
Alexandre> I don't see any reason to do it. I'd rather keep both
Alexandre> `--host=TRIPLET' and plain `TRIPLET'.
> The fact is that the two schemes were not equivalent. It is Ian who
> suggested twice that in these conditions, we shoul
> -Original Message-
> From: Akim Demaille [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, April 26, 2000 1:32 PM
> To: Alexandre Oliva
> Cc: Mo DeJong; Ian Lance Taylor; [EMAIL PROTECTED];
> [EMAIL PROTECTED]; [EMAIL PROTECTED]; APatche
> Subject: Re: Re
> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
Akim> It is Ian who suggested twice that in these conditions, we
Akim> should get rid of HOST as an argument.
So the proposal below still does this, but it is open to discussion.
This is a real proposal this time, I think we have reached
On 25 Apr 2000, Akim Demaille wrote:
> - don't document --target etc. when the AC_CANONICAL_TARGET etc. is not
> used
>
> - change the defaults to
> 1. build ?= config.guess
> 2. host ?= build
> 3. target ?= host
>
> - remove the support of HOST on the command line, because it is
> i
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> On Apr 25, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
>> Akim, I was with you up until this one. Why would you want to
>> remove the --host option?
Alexandre> I don't think that's what he's suggesting. I think he's
Alex
On Apr 25, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
> Akim, I was with you up until this one. Why would you want to remove the
> --host option?
I don't think that's what he's suggesting. I think he's suggesting to
remove the use of `./configure TRIPLET' as equivalent to `./configure
--host=TR
On 25 Apr 2000, Akim Demaille wrote:
> > "Ian" == Ian Lance Taylor <[EMAIL PROTECTED]> writes:
>
> Ian> Dying is definitely wrong. I am also inclined to vote against
> Ian> warnings.
>
> OK, then here is my revamped revamping. It does not include your
> suggestion for host != build => cro
> "Ian" == Ian Lance Taylor <[EMAIL PROTECTED]> writes:
Ian> Dying is definitely wrong. I am also inclined to vote against
Ian> warnings.
OK, then here is my revamped revamping. It does not include your
suggestion for host != build => cross-compiling yet. I'd rather have
this as a separat
From: Akim Demaille <[EMAIL PROTECTED]>
Date: 25 Apr 2000 16:34:11 +0200
Akim> I don't think dying is right: up to now the tradition in
Akim> Autoconf has always been ignore what could make sense in another
Akim> ./configure even if not the current one.
Well, I implemented a dy
22 matches
Mail list logo
