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 9776] New: libubox build failed
Date: Sat, 25 Mar 2017 08:54:36 +0000	[thread overview]
Message-ID: <bug-9776-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 9776
           Summary: libubox build failed
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: linhuikui at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

libubox: installs files in
/home/lhk/workspace/smdk2440/host/usr/arm-buildroot-linux-gnueabi/sysroot//home/lhk/workspace/smdk2440
package/pkg-generic.mk:255: recipe for target
'/home/lhk/workspace/smdk2440/build/libubox-290c64ef5b5c3e75be851594f269d6a9568e64e5/.stamp_staging_installed'
failed

above is the logs from linux console

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

             reply	other threads:[~2017-03-25  8:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-25  8:54 bugzilla at busybox.net [this message]
2017-03-25 13:36 ` [Buildroot] [Bug 9776] libubox build failed bugzilla at busybox.net
     [not found] ` <CAFOYHZA+Q-J3+591sPK21CY+i0PV+2d3LYTwD0EMhCtoLk_7+A@mail.gmail.com>
     [not found]   ` <CAFOYHZBZ0Fo8202HtObbrkv4bAMV2vu1mZvewf8G+Vgg7EJ9cg@mail.gmail.com>
2017-03-26  1:47     ` [Buildroot] [Bug 9776] New: " Chris Packham
2017-03-26  1:53       ` Chris Packham
2017-04-07  8:41 ` [Buildroot] [Bug 9776] " 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-9776-163@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.