mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Empty modules.dep after kernel update
Date: Wed, 22 Nov 2017 14:14:39 +0100	[thread overview]
Message-ID: <20171122131439.q3tr4thwc64heo5z@pengutronix.de> (raw)
In-Reply-To: <em32eaca17-6bb0-42cf-ba3b-48be49a07393@nb-mak>

Hi,

On Wed, Nov 22, 2017 at 12:27:28PM +0000, Matthias Klein wrote:
> I am working on a kernel update from 4.4 to 4.14 in our ptxdist 2016.04
> based BSP.
> 
> The kernel builds fine, but the modules.dep file is zero bytes long.
> I updated libkmod.make from version 22 to 24, but that did not help.
> 
> When I run the depmod from sysroot-host/sbin/ by hand it finds no symbols:
> 
> ./depmod -a -n -b ~/bsp/platform-xxx/root 4.14.1-00003-gb5f7a9a47e0b
> # Aliases extracted from modules themselves.
> # Soft dependencies extracted from modules themselves.
> # Aliases for symbols, used by symbol_request().
> 
> If I run the same with the old 4.4 path I get a lot of symbols / output
> ./depmod -a -n -b ~/bsp/platform-xxx/root 4.4.79
> 
> 
> Does anyone have an idea what could be wrong, or what I can check?

Does it work with 'depmod' from your host system? Maybe you enabled module
compression fo 4.14? That's currently disabled in host-libkmod.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2017-11-22 13:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22 12:27 Matthias Klein
2017-11-22 13:14 ` Michael Olbrich [this message]
2017-11-22 13:26   ` Matthias Klein

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=20171122131439.q3tr4thwc64heo5z@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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