All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9966] util-linux-2.30/.stamp_built' failed
Date: Wed, 28 Jun 2017 11:03:02 +0000	[thread overview]
Message-ID: <bug-9966-163-Vhjpx9CQI1@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9966-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=9966

Carlos Santos <casantos@datacom.ind.br> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WORKSFORME
             Status|ASSIGNED                    |RESOLVED

--- Comment #3 from Carlos Santos <casantos@datacom.ind.br> ---
Looks like the reporter attempted to perform a dirty build in an output
directory containing traces of a previous build, for a different architecture.

Closing as RESOLVED/WORKSFORME, since the reporter did not provide enough
information to reproduce the failure and was able to circumvent the problem by
means of a clean build.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2017-06-28 11:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-19 11:11 [Buildroot] [Bug 9966] New: util-linux-2.30/.stamp_built' failed bugzilla at busybox.net
2017-06-19 11:17 ` [Buildroot] [Bug 9966] " bugzilla at busybox.net
2017-06-26 11:07 ` bugzilla at busybox.net
2017-06-28  6:25 ` bugzilla at busybox.net
2017-06-28 11:03 ` bugzilla at busybox.net [this message]
2019-02-25  0:58 ` bugzilla at busybox.net
2019-02-25  1:02 ` bugzilla at busybox.net
2019-02-25  1:04 ` bugzilla at busybox.net
2019-02-25 11:44 ` bugzilla at busybox.net
2019-02-25 13:49 ` bugzilla at busybox.net
2019-02-25 16:51 ` bugzilla at busybox.net

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=bug-9966-163-Vhjpx9CQI1@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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 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.