9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: cinap_lenrek@gmx.de
To: 9fans@9fans.net
Subject: Re: [9fans] Kernel compile in Linuxemu
Date: Wed, 26 Aug 2009 19:11:58 +0200	[thread overview]
Message-ID: <69667cb8ca671bbe60d0df0af4a5ef2f@gmx.de> (raw)
In-Reply-To: <fe41879c0908231434l6afc496seba05e1b2347263b@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 58 bytes --]

fixed, try the latest version from sources.

--
cinap

[-- Attachment #2: Type: message/rfc822, Size: 3922 bytes --]

From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Kernel compile in Linuxemu
Date: Sun, 23 Aug 2009 17:34:59 -0400
Message-ID: <fe41879c0908231434l6afc496seba05e1b2347263b@mail.gmail.com>

Since I can't compile anything - let alone a kernel -
in my Acer Aspire One, I decided to try compiling
one under Linuxemu, with the hopes that I could
then copy the resulting kernel modules back to the
Acer and make use of them here.

However, 'make' under Linuxemu fails as such:

root@sounine:/usr/src/aspire/linux-2.6.23.9# make
cc1: stdout: Value too large for defined data type
cc1: stdout: Value too large for defined data type
  CHK    include/linux/version.h
  CHK    include/linux/utsrelease.h
  CALL   scripts/checksyscalls.sh
cc1: stdout: Value too large for defined data type
sed: couldn't flush stdout: Cannot send after transport endpoint shutdown
make[1]: *** [missing-syscalls] Error 1
make: *** [prepare0] Error 2

So, is this some limitation in Linuxemu or am I just
doing something wrong?

I'd be happy to provide more (debug) information if
it is required.


ak

  reply	other threads:[~2009-08-26 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-23 21:34 Akshat Kumar
2009-08-26 17:11 ` cinap_lenrek [this message]
2009-08-27  8:12   ` Akshat Kumar

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=69667cb8ca671bbe60d0df0af4a5ef2f@gmx.de \
    --to=cinap_lenrek@gmx.de \
    --cc=9fans@9fans.net \
    /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).