On Wed, 28 May 2014 11:16:09 +0200
Markus Armbruster wrote:
> Peter Maydell writes:
>
> > On 28 May 2014 09:46, 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=with
Peter Maydell writes:
> On 28 May 2014 09:46, 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 just explicitly
On Wed, 28 May 2014 09:52:38 +0100
Peter Maydell wrote:
> On 28 May 2014 09:46, 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
On 28 May 2014 09:46, 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 just explicitly specify --binary-files=binary,
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 just explicitly specify --binary-files=binary, which will
override any user settings and do what w
