Re: parisc 4.16-rc1 error: ERROR: "$$remU" [drivers/net/tun.ko] undefined!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 13.02.2018 20:55, Meelis Roos wrote:
>> On 2018-02-13 8:55 AM, Meelis Roos wrote:
>>>    MODPOST 9 modules
>>> ERROR: "$$remU" [drivers/net/tun.ko] undefined!
>>> make[1]: *** [scripts/Makefile.modpost:92: __modpost] Error 1
>> I believe $$remU comes from the millicode library milli.a.  It is bundled with
>> compiler.
>> Try adding V=1 to the make command so you can see the gcc command for the
>> above.
> 
> The command is modpost:
> 
>   find .tmp_versions -name '*.mod' | xargs -r grep -h '\.ko$' | sort -u | sed 's/\.ko$/.o/' | scripts/mod/modpost   -o ./Module.symvers    -S    -s -T -
> ERROR: "$$remU" [drivers/net/tun.ko] undefined!
> 
> hppa64-linux-objdump --disassemble drivers/net/tun.ko
> and
> hppa64-linux-nm drivers/net/tun.ko
> do not show any sign of the $$remU.
> 
> mroos@a500 ~/linux $ fgrep -r '$$remU' arch/parisc/ 
> arch/parisc/kernel/parisc_ksyms.c:extern void $$remU(void);
> arch/parisc/kernel/parisc_ksyms.c:EXPORT_SYMBOL($$remU);

Yes, that's correct.
The linux kernel executable should link in libgcc.a, thus include
the $$remU symbol (from libgcc.a) and then be able to export it to
linux kernel modules if necessary. 
 
> It's in /usr/lib/gcc/hppa64-unknown-linux-gnu/5.4.0/libgcc.a

Yes, it should be in some libgcc.a file which is linked into the kernel.
For me:
root@phantom:/usr/lib# hppa64-linux-gnu-objdump -x ./gcc/hppa64-linux-gnu/4.9/libgcc.a | grep remU | grep text
0000000000000000 g       .text  0000000000000144 .hidden $$remU


> CONFIG_CROSS_COMPILE="hppa64-linux-" - maybe modpost gets this wrong 
> somehow?

It says for you:
> ERROR: "$$remU" [drivers/net/tun.ko] undefined!

I would be astonished if $$remU hasn't been included in your kernel executable.

> mroos@a500 ~/linux $ file scripts/mod/modpost
> scripts/mod/modpost: ELF 32-bit MSB executable, PA-RISC, *unknown arch 0xf* version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld.so.1, for GNU/Linux 3.2.0, not stripped
> 
> This is strange, *unknown arch 0xf* ?? This hould be native binary... 
> yes, all my binaries under /bin have this arch, so my toolchain is 
> broken is some funny way...

That's normal and not related to your $$remU problem.

Helge
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux SoC]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux