From: moinejf@free.fr (Jean-Francois Moine)
To: linux-arm-kernel@lists.infradead.org
Subject: kernel 3.8 make problem
Date: Thu, 7 Feb 2013 11:12:06 +0100 [thread overview]
Message-ID: <20130207111206.153df673@armhf> (raw)
In-Reply-To: <20130206170638.GJ17833@n2100.arm.linux.org.uk>
On Wed, 6 Feb 2013 17:06:38 +0000
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> On Wed, Feb 06, 2013 at 06:03:05PM +0100, Jean-Francois Moine wrote:
> > I moved to make 3.82 and also libc6 2.17 (my Cubox runs Debian armhf
> > with kernel 3.8-rc6), and I can now make some programs (with make 2.81,
> > I was getting a seg fault of the child after the first vfork), but I
> > get the same errors when building a kernel. Does anybody have such a
> > problem?
>
> Are you using a 2G:2G VM split? If so, don't (really no reason to use
> that on the cubox.)
With 3/1 VM split, you cannot use at least 128Mb.
But, thanks, you are right: 'make' works with 3/1, but not with 2/2 nor 1/3.
The strangest thing is that all other programs seem to work fine.
What is the devil with make?
--
Ken ar c'henta? | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
next prev parent reply other threads:[~2013-02-07 10:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ttxj4oytvg02pxivwnruketi.1359554350723@email.android.com>
2013-01-30 14:07 ` kernel 3.8 make problem Jean-Francois Moine
2013-01-30 14:59 ` Florian Fainelli
2013-01-30 15:35 ` Jean-Francois Moine
2013-02-06 17:03 ` Jean-Francois Moine
2013-02-06 17:06 ` Russell King - ARM Linux
2013-02-07 10:12 ` Jean-Francois Moine [this message]
2013-02-07 11:03 ` Will Deacon
2013-02-07 14:37 ` kernel 3.8 make problem [solved] Jean-Francois Moine
2013-01-30 11:55 kernel 3.8 make problem Jean-Francois Moine
[not found] ` <2822D1C2B9B19F4A8261F756A13373F8CAF61C@DFLE12.ent.ti.com>
[not found] ` <20130130142515.0600bf1e@armhf>
[not found] ` <bedmt81oibwyqccqjqgpshjv.1359552548411@email.android.com>
2013-01-30 14:00 ` Jean-Francois Moine
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=20130207111206.153df673@armhf \
--to=moinejf@free.fr \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).