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 10536] Finding non-relative paths in the ccache
Date: Mon, 22 Jan 2018 15:28:08 +0000	[thread overview]
Message-ID: <bug-10536-163-XZGls5qQX5@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10536-163@https.bugs.busybox.net/>

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

--- Comment #5 from Mark Hirota <mhirota@impinj.com> ---
Arnout: yes, we have seen a failure as Trent describes, but with 2 similar
configs: r700 and r700_rescue.

>>> uboot-tools 2017.09 Building
PATH="/mnt/work/output/r700/host/bin:/mnt/work/output/r700/host/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
/usr/bin/make -j5 -C /mnt/work/output/r700/build/uboot-tools-2017.09
CROSS_COMPILE="/mnt/work/output/r700/host/bin/arm-buildroot-linux-gnueabihf-"
CFLAGS="-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64  -O3 
-fstack-protector-strong" LDFLAGS=""
STRIP=/mnt/work/output/r700/host/bin/arm-buildroot-linux-gnueabihf-strip
CROSS_BUILD_TOOLS=y tools-only
  CHK     include/config/uboot.release
  CHK     include/generated/timestamp_autogenerated.h
  HOSTCC  scripts/basic/fixdep
  UPD     include/generated/timestamp_autogenerated.h
  UPD     include/config/uboot.release
  CHK     include/generated/version_autogenerated.h
  UPD     include/generated/version_autogenerated.h
  HOSTCC  tools/mkenvimage.o
  WRAP    tools/lib/crc32.c
  HOSTCC  tools/os_support.o
  HOSTCC  tools/aisimage.o
  HOSTCC  tools/atmelimage.o
  WRAP    tools/common/bootm.c
  HOSTCC  tools/default_image.o
fixdep: error opening config file:
/mnt/work/output/r700_rescue/host/lib/gcc/arm-buildroot-linux-gnueabihf/7.2.0/include/stddef.h:
No such file or directory

Our build automation performs clean builds, but shares a buildroot-ccache
across them.  This type of failure forces us to build the projects on separate
build hosts to avoid hitting it.

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

  parent reply	other threads:[~2018-01-22 15:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 18:04 [Buildroot] [Bug 10536] New: Finding non-relative paths in the ccache bugzilla at busybox.net
2017-12-07 20:08 ` [Buildroot] [Bug 10536] " bugzilla at busybox.net
2017-12-07 20:15 ` bugzilla at busybox.net
2018-01-10 20:42 ` bugzilla at busybox.net
2018-01-17 22:44 ` bugzilla at busybox.net
2018-01-22 15:28 ` bugzilla at busybox.net [this message]
2018-01-22 17:57 ` bugzilla at busybox.net
2018-01-26 14:15 ` bugzilla at busybox.net
2018-01-26 14:17 ` bugzilla at busybox.net
2018-01-31 19:16 ` bugzilla at busybox.net
2018-01-31 19:29 ` 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-10536-163-XZGls5qQX5@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