On Fri, 06 Jun 2014 10:11:27 +0200
Paolo Bonzini wrote:
> Il 06/06/2014 09:41, Cornelia Huck ha scritto:
> > On Wed, 28 May 2014 12:39:17 +0200
> > Cornelia Huck wrote:
> >
> >> The check for big or little endianness relies on grep reporting
> >> match/non-match on the generated binary. If the u
Il 06/06/2014 09:41, Cornelia Huck ha scritto:
On Wed, 28 May 2014 12:39:17 +0200
Cornelia Huck wrote:
The check for big or little endianness relies on grep reporting
match/non-match on the generated binary. If the user specified
--binary-files=without-match in their GREP_OPTIONS, this will fa
On Wed, 28 May 2014 12:39:17 +0200
Cornelia Huck wrote:
> The check for big or little endianness relies on grep reporting
> match/non-match on the generated binary. If the user specified
> --binary-files=without-match in their GREP_OPTIONS, this will fail.
>
> Let's follow what autoconf does and
On 05/28/2014 04:39 AM, Cornelia Huck wrote:
> The check for big or little endianness relies on grep reporting
> match/non-match on the generated binary. If the user specified
> --binary-files=without-match in their GREP_OPTIONS, this will fail.
>
> Let's follow what autoconf does and unset GREP_O
The check for big or little endianness relies on grep reporting
match/non-match on the generated binary. If the user specified
--binary-files=without-match in their GREP_OPTIONS, this will fail.
Let's follow what autoconf does and unset GREP_OPTIONS and CLICOLOR_FORCE
at the beginning of the scrip
