From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable <stable@vger.kernel.org>
Subject: Re: Build failures in v4.4.y.queue, v4.9.queue
Date: Mon, 8 Jul 2019 15:55:19 +0200 [thread overview]
Message-ID: <20190708135519.GA2900@kroah.com> (raw)
In-Reply-To: <1d749d61-a489-11e2-bb6b-21408e1057ff@roeck-us.net>
On Mon, Jul 08, 2019 at 06:21:31AM -0700, Guenter Roeck wrote:
> Various cris builds:
>
> init/built-in.o: In function `repair_env_string':
> main.c:(.init.text+0x106): undefined reference to `abort'
> arch/cris/mm/built-in.o: In function `do_page_fault':
> (.text+0x44e): undefined reference to `abort'
> arch/cris/mm/built-in.o: In function `mem_init':
> (.init.text+0x12): undefined reference to `abort'
> arch/cris/arch-v10/kernel/built-in.o: In function `cris_request_io_interface':
> (.text+0x219e): undefined reference to `abort'
> arch/cris/arch-v10/kernel/built-in.o: In function `cris_free_io_interface':
> (.text+0x2644): undefined reference to `abort'
> kernel/built-in.o:(.text+0x416): more undefined references to `abort' follow
>
> Caused by commit commit b068c10cde7f3e ("bug.h: work around GCC PR82365 in BUG()").
> Reverting it fixes the problem. I would suggest to undo the cris specific changes
> in that backport. An alternative would be for me to stop build-testing for the
> architecture if there is no further interest in keeping it alive for older branches.
Odd, why doesn't that trigger in mainline?
Oh, cris is gone upstream, that makes sense. I'll just go drop that
hunk from the patches so that things keep building.
thanks,
greg k-h
next prev parent reply other threads:[~2019-07-08 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 13:21 Build failures in v4.4.y.queue, v4.9.queue Guenter Roeck
2019-07-08 13:55 ` Greg Kroah-Hartman [this message]
2019-07-08 14:01 ` Guenter Roeck
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=20190708135519.GA2900@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux@roeck-us.net \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.