From: "Tej Parkash" <tejparkash.d@gmail.com>
To: sam@ravnborg.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux-kernel-digest Digest, Vol 32, Issue 795
Date: Wed, 30 May 2007 20:07:53 +0530 [thread overview]
Message-ID: <2bd9ebfa0705300737t4f11ee71mca114b37a969db01@mail.gmail.com> (raw)
In-Reply-To: <2bd9ebfa0705300735l51dcf4ceubf7f83ab44703010@mail.gmail.com>
On 5/30/07, Tej Parkash <tejparkash.d@gmail.com> wrote:
> > > >
> > > > 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.
yaa i got the warning but as i said building stage is also getting
terminated, without any error.
> 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
>
>
I don't think so that RAM or SWAP space is a constraint, is it related
to kernel build option or some change in arch. config files
I am not aware of the required patches for the same.
thanks
TEJ
next parent reply other threads:[~2007-05-30 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.13746.1180510421.20629.linux-kernel-digest@lists.us.dell.com>
[not found] ` <2bd9ebfa0705300735l51dcf4ceubf7f83ab44703010@mail.gmail.com>
2007-05-30 14:37 ` Tej Parkash [this message]
2007-05-30 15:12 ` Linux-kernel-digest Digest, Vol 32, Issue 795 Sam Ravnborg
2007-05-30 15:22 ` Tej Parkash
2007-05-30 15:36 ` Sam Ravnborg
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=2bd9ebfa0705300737t4f11ee71mca114b37a969db01@mail.gmail.com \
--to=tejparkash.d@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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.