automake-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] {compilers-for-testsuite} readme: how to run the testsuite w


From: Stefano Lattarini
Subject: Re: [PATCH] {compilers-for-testsuite} readme: how to run the testsuite with cross-compilers
Date: Tue, 20 Dec 2011 14:31:56 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.24) Gecko/20111114 Icedove/3.1.16

On 12/20/2011 02:18 PM, Peter Rosin wrote:
> Stefano Lattarini skrev 2011-12-20 12:13:
>
>> diff --git a/tests/README b/tests/README
>> index 980299d..4d7f21d 100644
>> --- a/tests/README
>> +++ b/tests/README
>> @@ -29,18 +29,18 @@ Running the tests
>>      make -k check TESTS="foo.test bar.test"             (GNU make)
>>      env TESTS="foo.test bar.test" make -e -k check      (non-GNU make)
>>  
>> - To run the tests in cross-compilation mode:
>> -
>> -    make -k check host_alias="$host_alias"              (GNU make)
>> -    env host_alias="$host_alias" make -e -k check       (non-GNU make)
>> -
>> - Here `$host_alias' should be defined to a proper value different from
>> - configure-determined `$build_alias', and should refer to a set of
>> - cross-compilers you have available on your system; for example, if
>> - on Linux you have a set of MinGW-targeted cross-compilers named
>> - 'i586-mingw32msvc-cc', 'i586-mingw32msvc-c++', etc., you could use:
>> -
>> -   make -k check host_alias='i586-mingw32msvc'
>> + To run the tests in cross-compilation mode, you should first configure
>> + the automake source tree to a cross-compilation setup.  For example, to
>> + run with a Linux-to-Cygwin cross compiler, you will need something like
> 
> I think you mean Linux-to-MinGW here,
>
Oops, you're right; fixed.

> Linux-to-Cygwin is not as common...
> 
>> + this:
>> +
>> +   ./configure --host i586-mingw32msvc --build i686-pc-linux-gnu
> 
> ...and this is the proof. :-)
>
Eh eh ;-)

 > Still, RMS might want you to say GNU/Linux-to-MinGW. Your call!
>
"Linux-to-MinGW", while a little more imprecise, is shorter and sounds clearer,
so I'll stick with it.  This would probably be a bad call in any official GNU
documentation, but this is just a README that favors brevity and clarity over
completeness.

>> + To avoid possible spurious error, you really have to *explicitly* specify
>> + `--build' in addition to `--host'; the `lib/config.guess' script can help
>> + you in determining what is the correct value you should pass to `--build'.
> 
> I would write the last part of the above like this:
> 
> the `lib/config.guess' script can help determine the correct value to pass
> to `--build'.
>
Shorter and clearer; I'll use you wording.

I will push the patch shortly, after rebasing 
`experimental/compilers-for-testsuite'
on latest `testsuite-work'.

Thanks,
  Stefano



reply via email to

[Prev in Thread] Current Thread [Next in Thread]