On 2021-03-01 4:34 p.m., Helge Deller wrote:
> I think the only way to fix this in a clean way is to
> enable CONFIG_MLONGCALLS, which lets gcc use -mlong-calls compiler
> option and thus creates far calls.
That's currently the only way to work around the R_PARISC_PCREL22F relocation
error. We
kernel/rcu/refscale.o(.init.text+0x228): cannot reach
schedule_timeout_uninterruptible
hppa64-linux-ld: kernel/time/timekeeping.o(.init.text+0x228): cannot reach
_raw_spin_lock_irqsave
hppa64-linux-ld: kernel/time/timekeeping.o(.init.text+0x320): cannot reach
_raw_spin_unlock_irqr
; > _raw_write_unlock
> > > hppa64-linux-ld: kernel/time/clocksource.o(.init.text+0x90): cannot
> > > reach mutex_lock
> > > hppa64-linux-ld: kernel/time/clocksource.o(.init.text+0xc4): cannot
> > > reach mutex_unlock
> > > hppa64-linux-ld: kernel/
hppa64-linux-ld: kernel/workqueue.o(.init.text+0x388): cannot reach
mutex_unlock
hppa64-linux-ld: kernel/user.o(.init.text+0x80): cannot reach
_raw_spin_lock_irq
hppa64-linux-ld: kernel/user.o(.init.text+0xb8): cannot reach
_raw_spin_unlock_irq
hppa64-linux-ld: kernel/rcu/refscale.o(.ini
eue.o(.init.text+0x128): cannot reach
> mutex_unlock
>hppa64-linux-ld: kernel/workqueue.o(.init.text+0x354): cannot reach
> mutex_lock
>hppa64-linux-ld: kernel/workqueue.o(.init.text+0x388): cannot reach
> mutex_unlock
>hppa64-linux-ld: kernel/user.o(.init.text+0x80): c
user.o(.init.text+0x80): cannot reach
_raw_spin_lock_irq
hppa64-linux-ld: kernel/user.o(.init.text+0xb8): cannot reach
_raw_spin_unlock_irq
>> hppa64-linux-ld: kernel/rcu/refscale.o(.init.text+0x228): cannot reach
>> schedule_timeout_uninterruptible
hppa64-linux-ld: kernel/time/timeke
6 matches
Mail list logo