On 16.07.2012, at 20:28, Peter Maydell wrote:
> On 16 July 2012 18:24, Alexander Graf wrote:
>> On 07/16/2012 05:40 PM, Peter Maydell wrote:
>>> Hmm, good point -- unlike the actual program compile, failures
>>> due to -Werror inside configure are silent and near-invisible.
>>> Maybe we should b
On 16 July 2012 18:24, Alexander Graf wrote:
> On 07/16/2012 05:40 PM, Peter Maydell wrote:
>> Hmm, good point -- unlike the actual program compile, failures
>> due to -Werror inside configure are silent and near-invisible.
>> Maybe we should back out 417c9d72 ?
>
> So how do we deal with the orig
On 07/16/2012 05:40 PM, Peter Maydell wrote:
On 16 July 2012 16:35, Eric Blake wrote:
On 07/15/2012 07:54 AM, Stefan Weil wrote:
Since commit 417c9d72d48275d19c60861896efd4962d21aca2 all configure tests
normally run with -Werror. Some of these tests now fail because they
raised a compiler warn
On 16 July 2012 16:35, Eric Blake wrote:
> On 07/15/2012 07:54 AM, Stefan Weil wrote:
>> Since commit 417c9d72d48275d19c60861896efd4962d21aca2 all configure tests
>> normally run with -Werror. Some of these tests now fail because they
>> raised a compiler warning.
> Nothing wrong with this patch,
On 07/15/2012 07:54 AM, Stefan Weil wrote:
> Since commit 417c9d72d48275d19c60861896efd4962d21aca2 all configure tests
> normally run with -Werror. Some of these tests now fail because they
> raised a compiler warning.
>
> This patch fixes support for capabilities.
>
> Signed-off-by: Stefan Weil
Since commit 417c9d72d48275d19c60861896efd4962d21aca2 all configure tests
normally run with -Werror. Some of these tests now fail because they
raised a compiler warning.
This patch fixes support for capabilities.
Signed-off-by: Stefan Weil
---
configure |2 +-
1 file changed, 1 insertion(+)
