From: John David Anglin <dave.anglin@bell.net>
To: Meelis Roos <mroos@linux.ee>, linux-parisc@vger.kernel.org
Subject: Re: parisc 4.16-rc1 error: ERROR: "$$remU" [drivers/net/tun.ko] undefined!
Date: Tue, 13 Feb 2018 14:31:05 -0500 [thread overview]
Message-ID: <5abecbed-e50f-e41c-1fd1-a7bcc4768f2a@bell.net> (raw)
In-Reply-To: <alpine.LRH.2.21.1802131552240.9153@math.ut.ee>
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.
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2018-02-13 19:31 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 [this message]
2018-02-13 19:55 ` Meelis Roos
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=5abecbed-e50f-e41c-1fd1-a7bcc4768f2a@bell.net \
--to=dave.anglin@bell.net \
--cc=linux-parisc@vger.kernel.org \
--cc=mroos@linux.ee \
/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