Build failures in v4.4.y.queue, v4.9.queue

Build failures in v4.4.y.queue, v4.9.queue

[Guenter Roeck]

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.

Guenter

Re: Build failures in v4.4.y.queue, v4.9.queue

[Greg Kroah-Hartman]

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

Re: Build failures in v4.4.y.queue, v4.9.queue

[Guenter Roeck]

On 7/8/19 6:55 AM, Greg Kroah-Hartman wrote:
> 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.
> 

It builds in v4.14.y.queue, so I assume there must be additional context patches
making it work. Tracking those down didn't seem to be worth the effort.

Guenter