All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch-fe.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [meta-qt5][fido] commit 699e1570e6 breaks build
Date: Thu, 28 May 2015 12:30:26 +0200	[thread overview]
Message-ID: <5566EE42.7070503@dresearch-fe.de> (raw)
In-Reply-To: <1432806496.404.103.camel@linuxfoundation.org>

On 28.05.2015 11:48, Richard Purdie wrote:
> On Thu, 2015-05-28 at 11:39 +0200, Steffen Sledz wrote:
>> Commit 699e1570e66cb28e4bfd0eb15d41f3af2bed5b62 (autotools: Fix find
>> races on source directory) in fido branch of openembedded-core breaks
>> build (do_configure) of qtbase-native from meta-qt5 fido branch. :(
> 
> I'm struggling to see exactly how this commit could result in this kind
> of failure. How did you deduce that this was the problem?

By trying step by step one commit (in openembedded-core) after another.

> Is the problem not that qtbase-native doesn't rebuild cleanly if
> configure is re-executed? Have you tried cleaning qtbase-native and
> rebuilding it?

I're checked this. A clean build or a "bitbake -c cleansstate qtbase-native" avoids this problem.

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058


  reply	other threads:[~2015-05-28 10:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28  9:39 [meta-qt5][fido] commit 699e1570e6 breaks build Steffen Sledz
2015-05-28  9:48 ` Richard Purdie
2015-05-28 10:30   ` Steffen Sledz [this message]
2015-05-28 10:01 ` Martin Jansa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5566EE42.7070503@dresearch-fe.de \
    --to=sledz@dresearch-fe.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=richard.purdie@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.