From: Antony Pavlov <antonynpavlov@gmail.com>
To: barebox@lists.infradead.org
Subject: Fw: next: sandbox: arch/sandbox/os/common.c:31:18: fatal error: init.h: No such file or directory
Date: Mon, 29 Jun 2015 13:55:01 +0300 [thread overview]
Message-ID: <20150629135501.344827695c942d496959aa1e@gmail.com> (raw)
Sorry!
I have forgotten to add barebox@list.infradead.org to CC.
Begin forwarded message:
Date: Mon, 29 Jun 2015 13:11:12 +0300
From: Antony Pavlov <antonynpavlov@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>, Juergen Borleis <jbe@pengutronix.de>
Subject: next: sandbox: arch/sandbox/os/common.c:31:18: fatal error: init.h: No such file or directory
Hi!
It looks like sandbox barebox from next branch is broken.
How to reproduce the problem
$ cd barebox.git
$ git checkout next
$ git show -1
commit 5e98d4ec2d434e20a4044ec5d5897ae7b51f9411
Merge: 9175369 3c36a73
Author: Sascha Hauer <s.hauer@pengutronix.de>
Date: Mon Jun 29 07:25:47 2015 +0200
Merge branch 'for-next/watchdog' into next
$ unset ARCH
$ unset CROSS_COMPILE
$ make sandbox_defconfig
...
$ make
...
CC arch/sandbox/os/common.o
arch/sandbox/os/common.c:31:18: fatal error: init.h: No such file or directory
#include <init.h>
^
compilation terminated.
git-bisect reports that
0c142e405712586ed8074ce0166c515e158cc986 is the first bad commit
commit 0c142e405712586ed8074ce0166c515e158cc986
Author: Juergen Borleis <jbe@pengutronix.de>
Date: Thu Jun 25 09:34:34 2015 +0200
System restart: add a scope value to the system restart feature
--
Best regards,
Antony Pavlov
--
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2015-06-29 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 10:55 Antony Pavlov [this message]
2015-06-29 11:26 ` Sascha Hauer
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=20150629135501.344827695c942d496959aa1e@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
/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