From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10276] BR2_PACKAGE_LINUX_TOOLS_GPIO fails for MIPS with "gpio-hammer.o: ABI is incompatible with that of the selected emulation"
Date: Wed, 30 Aug 2017 17:55:48 +0000 [thread overview]
Message-ID: <bug-10276-163-E8Lisphr86@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10276-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10276
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at buildroot.uclibc |yann.morin.1998 at free.fr
|.org |
Status|NEW |ASSIGNED
CC| |yann.morin.1998 at free.fr
--- Comment #2 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Given the following:
CC gpio-utils.o
LD gpio-event-mon-in.o
gpio-utils.o: file not recognized: File truncated
/data/git/buildroot/output/build/linux-4.11.3/tools/build/Make
file.build:149: recipe for target 'gpio-event-mon-in.o' failed
it looks like it might be a parallel build issue, where gpio-event-mon-in.o
needs gpio-utils.o, but it is not yet built.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-08-30 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 5:38 [Buildroot] [Bug 10276] New: BR2_PACKAGE_LINUX_TOOLS_GPIO fails for MIPS with "gpio-hammer.o: ABI is incompatible with that of the selected emulation" bugzilla at busybox.net
2017-08-30 8:32 ` [Buildroot] [Bug 10276] " bugzilla at busybox.net
2017-08-30 17:55 ` bugzilla at busybox.net [this message]
2017-08-30 18:05 ` bugzilla at busybox.net
2017-08-30 19:06 ` bugzilla at busybox.net
2024-06-15 14:47 ` bugzilla
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-10276-163-E8Lisphr86@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.