linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Subject: [PATCH] frv: fix build failure
Date: Tue, 21 Nov 2017 22:10:33 +0000	[thread overview]
Message-ID: <1511302233-5008-1-git-send-email-sudipm.mukherjee@gmail.com> (raw)

The frv defconfig build is failing with the error:
lib/mpi/mpih-div.o: In function `mpihelp_divrem':
mpih-div.c:(.text+0x30c): undefined reference to `abort'

The function 'abort' was never defined for the frv architecture.
Create 'abort' as is done in other arch like 'arm' and 'unicore32'.

Signed-off-by: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
---

The build log of next-20171121 is at:
https://travis-ci.org/sudipm-mukherjee/parport/jobs/305076731

 arch/frv/kernel/traps.c | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/arch/frv/kernel/traps.c b/arch/frv/kernel/traps.c
index fb08ebe..70f4387 100644
--- a/arch/frv/kernel/traps.c
+++ b/arch/frv/kernel/traps.c
@@ -633,6 +633,15 @@ void show_backtrace(struct pt_regs *frame, unsigned long sp)
 
 } /* end show_backtrace() */
 
+void abort(void)
+{
+	BUG();
+
+	/* if that doesn't kill us, halt */
+	panic("Oops failed to kill thread");
+}
+EXPORT_SYMBOL(abort);
+
 /*****************************************************************************/
 /*
  * initialise traps
-- 
1.9.1

             reply	other threads:[~2017-11-21 22:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21 22:10 Sudip Mukherjee [this message]
2017-11-23 17:17 ` [PATCH] frv: fix build failure Alexey Brodkin
2017-11-23 23:01   ` Sudip Mukherjee
2017-11-24  5:02     ` Alexey Brodkin
2017-11-27 18:25   ` Vineet Gupta
2017-12-03 22:32     ` Sudip Mukherjee
2017-12-06 22:00       ` Vineet Gupta
2017-11-27 18:49 ` Geert Uytterhoeven

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=1511302233-5008-1-git-send-email-sudipm.mukherjee@gmail.com \
    --to=sudipm.mukherjee@gmail.com \
    --cc=akpm@linux-foundation.org \
    --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;
as well as URLs for NNTP newsgroup(s).