All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neuer User <auslands-kv@gmx.de>
To: yocto@yoctoproject.org
Subject: Re: [meta-qt5] How to bisect problem?
Date: Wed, 22 Oct 2014 08:39:08 +0200	[thread overview]
Message-ID: <m27jec$fuo$1@ger.gmane.org> (raw)
In-Reply-To: <20141021165612.GF2455@jama>

Am 21.10.2014 um 18:56 schrieb Martin Jansa:
> qt5 isn't special from this perspective (well maybe except that it takes
> damn long to build it all, so it's always useful to narrow the
> problematic module asap and then rebuild only that one as long as
> dependencies on other modules allow), I would start by using 5.3.0
> and 5.3.1 (because you'll easily find meta-qt5 revisions which will give
> you compatible set of qt5 tarballs).
> 
> If you plan to upgrade your images to 5.4.* soon(ish), than testing
> 5.4-alpha (or 5.4-beta from jansa/master branch) is also very useful,
> but I would expect more rough road then just bisecting 5.3.* releases.
> 
> Cheers,
> 

Thanks. So, I will do the following:
- first priority is to get the shellshock update ready (that was the
reason why I started the update nightmare at all)
- then I will try 5.3.1 and 5.3.0 to see if the problem is already in there
- I need to do some qt5 work anyway as one of the next steps is to get
the "camera" module working (which doesn't work on my imx6 system)

I will probably be back here then :-)

Cheers

Michael




      reply	other threads:[~2014-10-22  6:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 15:39 [meta-qt5] How to bisect problem? Neuer User
2014-10-21 16:56 ` Martin Jansa
2014-10-22  6:39   ` Neuer User [this message]

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='m27jec$fuo$1@ger.gmane.org' \
    --to=auslands-kv@gmx.de \
    --cc=yocto@yoctoproject.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.