From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: linux-am33-list@redhat.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: mn10300 build fails
Date: Sat, 13 Jun 2015 17:44:55 +0530 [thread overview]
Message-ID: <20150613121455.GA17555@sudip-PC> (raw)
Hi David,
I was trying to build mn10300 today and I got build failure.
I was following the steps of kbuild test robot <fengguang.wu@intel.com>
like:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
and then I tried:
make.cross ARCH=mn10300 allmodconfig
make.cross ARCH=mn10300
again i tried with allyesconfig.
but in both cases build failed with:
error: invalid use of undefined type 'struct kprobe_ctlblk'
am i missing anything or is the build broken?
besides build failure it has got tons of build warning and
20 unimplemented syscalls.
previously also I tried to mail you and Koichi Yasutake asking about the
board I need, to start working with this architecture. But mails to
Koichi Yasutake bounced back and you never replied. :(
regards
sudip
reply other threads:[~2015-06-13 12:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150613121455.GA17555@sudip-PC \
--to=sudipm.mukherjee@gmail.com \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-am33-list@redhat.com \
--cc=linux-kernel@vger.kernel.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