From: Meelis Roos <mroos@linux.ee>
To: John David Anglin <dave.anglin@bell.net>
Cc: linux-parisc@vger.kernel.org
Subject: Re: parisc 4.16-rc1 error: ERROR: "$$remU" [drivers/net/tun.ko] undefined!
Date: Tue, 13 Feb 2018 21:55:00 +0200 (EET) [thread overview]
Message-ID: <alpine.LRH.2.21.1802132145050.24929@math.ut.ee> (raw)
In-Reply-To: <5abecbed-e50f-e41c-1fd1-a7bcc4768f2a@bell.net>
> 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);
It's in /usr/lib/gcc/hppa64-unknown-linux-gnu/5.4.0/libgcc.a
CONFIG_CROSS_COMPILE="hppa64-linux-" - maybe modpost gets this wrong
somehow?
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...
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2018-02-13 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 13:55 parisc 4.16-rc1 error: ERROR: "$$remU" [drivers/net/tun.ko] undefined! Meelis Roos
2018-02-13 19:31 ` John David Anglin
2018-02-13 19:55 ` Meelis Roos [this message]
2018-02-13 20:18 ` Helge Deller
2018-02-14 14:20 ` Meelis Roos
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=alpine.LRH.2.21.1802132145050.24929@math.ut.ee \
--to=mroos@linux.ee \
--cc=dave.anglin@bell.net \
--cc=linux-parisc@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