Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Fatih Aşıcı" <fatih.asici@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-07-20
Date: Mon, 21 Jul 2014 14:16:00 +0300	[thread overview]
Message-ID: <201407211416.00389.fatih.asici@gmail.com> (raw)
In-Reply-To: <20140721121553.10be890c@free-electrons.com>

On Monday 21 July 2014 13:15:53 Thomas Petazzoni wrote:
> >        arm |            qt5multimedia-5.3.1 | NOK |
> >http://autobuild.buildroot.net/results/b975c4bb8aebad2d0b8eaefc98c42c0460
> >ace5be/ mips64el |            qt5multimedia-5.3.1 | NOK |
> >http://autobuild.buildroot.net/results/b1ca9c845f1cf3a396cbd7ad81bfc44119
> >74c709/
> 
> ^[[7m>>> qt5multimedia 5.3.1 Installing to target^[[27m
> cp -dpfr
> /home/test/autobuild/instance-3/output/host/usr/arm-buildroot-linux-gnueab
> ihf/sysroot/usr/qml/* /home/test/autobuild/instance-3/output/target/usr/qml
> cp: cannot stat
> `/home/test/autobuild/instance-3/output/host/usr/arm-buildroot-linux-gnuea
> bihf/sysroot/usr/qml/*': No such file or directory
> 
> Fatih?
> 
> It might be related to the fact that I haven't applied your entire
> patch series.. but it would mean that your series was not
> bisectable! :-)

Sorry, the first patch in my series introduced this issue. I will send another 
patch which is based on my series.

Sometimes I forget removing output directory before testing a different config 
(building qt5multimedia w/o qt5declarative in this case).

  reply	other threads:[~2014-07-21 11:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-07-20 Thomas Petazzoni
2014-07-21 10:15 ` Thomas Petazzoni
2014-07-21 11:16   ` Fatih Aşıcı [this message]
2014-07-21 12:21   ` Gustavo Zacarias

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=201407211416.00389.fatih.asici@gmail.com \
    --to=fatih.asici@gmail.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox