Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 19:06:20 +0000	[thread overview]
Message-ID: <bug-10276-163-jjhIzHDO6J@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10276-163@https.bugs.busybox.net/>

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

--- Comment #4 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Thomas, I can very easily reproduce the truncated file issue, and it
indeed always happen with parallel builds, but not always.

And I can even reproduce it in a native build, on Linus' linux master:

$ make -j1000
mkdir -p include/linux 2>&1 || true
ln -sf /home/ymorin/dev/linux/linux/tools/gpio/../../include/uapi/linux/gpio.h
include/linux/gpio.h
make -f /home/ymorin/dev/linux/linux/tools/build/Makefile.build dir=.
obj=lsgpio
make -f /home/ymorin/dev/linux/linux/tools/build/Makefile.build dir=.
obj=gpio-hammer
make -f /home/ymorin/dev/linux/linux/tools/build/Makefile.build dir=.
obj=gpio-event-mon
make[1]: Entering directory '/home/ymorin/dev/linux/linux/tools/gpio'
make[1]: Entering directory '/home/ymorin/dev/linux/linux/tools/gpio'
make[1]: Entering directory '/home/ymorin/dev/linux/linux/tools/gpio'
  CC       gpio-event-mon.o
  CC       lsgpio.o
  CC       gpio-hammer.o
  CC       gpio-utils.o
  CC       gpio-utils.o
  CC       gpio-utils.o
gpio-event-mon.c: In function ?monitor_device?:
gpio-event-mon.c:100:19: warning: format ?%lu? expects argument of type ?long
unsigned int?, but argument 3 has type ?__u64 {aka long long unsigned int}?
[-Wformat=]
   fprintf(stdout, "GPIO EVENT %" PRIu64 ": ", event.timestamp);
                   ^~~~~~~~~~~~~~
  LD       gpio-event-mon-in.o
gpio-utils.o: file not recognized: File truncated
/home/ymorin/dev/linux/linux/tools/build/Makefile.build:143: recipe for target
'gpio-event-mon-in.o' failed
make[1]: *** [gpio-event-mon-in.o] Error 1
make[1]: Leaving directory '/home/ymorin/dev/linux/linux/tools/gpio'
Makefile:58: recipe for target 'gpio-event-mon-in.o' failed
make: *** [gpio-event-mon-in.o] Error 2
make: *** Waiting for unfinished jobs....
  LD       lsgpio-in.o
make[1]: Leaving directory '/home/ymorin/dev/linux/linux/tools/gpio'
  LD       gpio-hammer-in.o
make[1]: Leaving directory '/home/ymorin/dev/linux/linux/tools/gpio'


Yet, you are right that there is also (and more importantly) a
problem with using ld instead of gcc.

So, there are two issues in one. ;-)

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

  parent reply	other threads:[~2017-08-30 19:06 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
2017-08-30 18:05 ` bugzilla at busybox.net
2017-08-30 19:06 ` bugzilla at busybox.net [this message]
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-jjhIzHDO6J@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox