From: Sam Ravnborg <sam@ravnborg.org>
To: Tej Parkash <tejparkash.d@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: warning while building module.
Date: Wed, 30 May 2007 08:39:31 +0200 [thread overview]
Message-ID: <20070530063931.GA12203@uranus.ravnborg.org> (raw)
In-Reply-To: <20070529185725.GC5846@uranus.ravnborg.org>
On Tue, May 29, 2007 at 08:57:25PM +0200, Sam Ravnborg wrote:
> On Tue, May 29, 2007 at 10:15:58AM +0530, Tej Parkash wrote:
> > hi all
> >
> > while building module i was getting following warning and it terminate
> > module building stage
> The below are only warnings and your build should succeed.
>
> It is obviously i386 - is it a clean allmodconfig or any changes?
> Is it latest -linus or some older version of the codebase?
Did an allmodconfig build of i386 - I see (almost) all warnings here.
So I will take a look based on this.
The MODPOST stage took a while but it proceeded with no hick-ups.
MDOPSOT deals with ~2000 modules in my case and that consumes a bit
of memory. Maybe you are hitting the limit with respect to available RAM / SWAP?
Sam
prev parent reply other threads:[~2007-05-30 6:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 4:45 Tej Parkash
2007-05-29 18:57 ` Sam Ravnborg
2007-05-30 6:39 ` Sam Ravnborg [this message]
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=20070530063931.GA12203@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tejparkash.d@gmail.com \
/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
all inboxes | Powered by JetHome®