All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>,
	lkml List <linux-kernel@vger.kernel.org>
Subject: Re: How to link a .o with all modules
Date: Mon, 5 May 2008 22:44:49 +0200	[thread overview]
Message-ID: <20080505204449.GA9446@uranus.ravnborg.org> (raw)
In-Reply-To: <D346E2E4-26C3-482E-ABBF-AF1EE97E91CD@kernel.crashing.org>

> >
> >
> >Let me know if this does address your question.
> 
> The problem is MODPOST complains about undefined symbols:
> 
>   MODPOST 24 modules
> ERROR: "_restgpr_20_x" [net/key/af_key.ko] undefined!
> ERROR: "_restgpr_25_x" [net/key/af_key.ko] undefined!
> ERROR: "_restgpr_30_x" [net/key/af_key.ko] undefined!

I need a bit more context to try to analyse this.
Where did you expect _restgpr_20_x to be defined.
If in vmlinux then were they present in the
Module.symvers file?

If in the linked in .o file - could you
see the symbols using objdump.

etc.

Sorry - not much help right away.

PS. Travelling - do not expect responses until the
weekend.

	Sam

WARNING: multiple messages have this Message-ID (diff)
From: Sam Ravnborg <sam@ravnborg.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: lkml List <linux-kernel@vger.kernel.org>,
	"linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>
Subject: Re: How to link a .o with all modules
Date: Mon, 5 May 2008 22:44:49 +0200	[thread overview]
Message-ID: <20080505204449.GA9446@uranus.ravnborg.org> (raw)
In-Reply-To: <D346E2E4-26C3-482E-ABBF-AF1EE97E91CD@kernel.crashing.org>

> >
> >
> >Let me know if this does address your question.
> 
> The problem is MODPOST complains about undefined symbols:
> 
>   MODPOST 24 modules
> ERROR: "_restgpr_20_x" [net/key/af_key.ko] undefined!
> ERROR: "_restgpr_25_x" [net/key/af_key.ko] undefined!
> ERROR: "_restgpr_30_x" [net/key/af_key.ko] undefined!

I need a bit more context to try to analyse this.
Where did you expect _restgpr_20_x to be defined.
If in vmlinux then were they present in the
Module.symvers file?

If in the linked in .o file - could you
see the symbols using objdump.

etc.

Sorry - not much help right away.

PS. Travelling - do not expect responses until the
weekend.

	Sam

  reply	other threads:[~2008-05-05 20:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-04 18:22 How to link a .o with all modules Kumar Gala
2008-05-04 18:22 ` Kumar Gala
2008-05-04 19:24 ` Sam Ravnborg
2008-05-04 19:24   ` Sam Ravnborg
2008-05-05 14:46   ` Kumar Gala
2008-05-05 14:46     ` Kumar Gala
2008-05-05 20:44     ` Sam Ravnborg [this message]
2008-05-05 20:44       ` Sam Ravnborg
2008-05-08 14:16       ` Kumar Gala
2008-05-08 14:16         ` Kumar Gala
2008-05-08 20:22         ` Sam Ravnborg
2008-05-08 20:22           ` Sam Ravnborg
2008-05-09 13:52           ` Kumar Gala
2008-05-09 13:52             ` Kumar Gala
2008-05-12 15:51             ` Kumar Gala
2008-05-12 15:51               ` Kumar Gala
2008-06-03  4:55           ` Kumar Gala
2008-06-03  4:55             ` Kumar Gala
2008-05-04 23:27 ` H. Peter Anvin
2008-05-04 23:27   ` H. Peter Anvin
2008-05-04 23:38   ` Paul Mackerras
2008-05-04 23:38     ` Paul Mackerras

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=20080505204449.GA9446@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=galak@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.