All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Semler <cijoml@volny.cz>
To: rmk@arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: can't compile
Date: Mon, 24 Feb 2003 22:06:56 +0100	[thread overview]
Message-ID: <E18nPoV-0000XD-00@notas> (raw)

Hello,

I wanted compile my own kernel for iPAQ 3630 - 2.4.21 - because of new 
Bluetooth rfcomm.o support and other things, but I can't go nor through 
menuconfig :( My original platform is i386 (Intel Pentium III) - debian woody 
3.0r1

Liboc01:/usr/src/linux# make menuconfig ARCH=arm
rm -f include/asm-arm/arch include/asm-arm/proc
(cd include/asm-arm; ln -sf arch- arch; ln -sf proc- proc)
rm -f include/asm
( cd include ; ln -sf asm-arm asm)
make -C scripts/lxdialog all
make[1]: Entering directory `/usr/src/linux-2.4.20/scripts/lxdialog'
make[1]: Leaving directory `/usr/src/linux-2.4.20/scripts/lxdialog'
/bin/sh scripts/Menuconfig arch/arm/config.in
Using defaults found in arch/arm/defconfig
Preparing scripts: functions, parsingscripts/Menuconfig: line 1:   820 
Segmentation fault      awk "$1"
Awk died with error code 139. Giving up.
make: *** [menuconfig] Error 1

ARCH=ppc for example goes right
problem under 2.4.19, 2.4.20, 2.4.21-pre4 - older kernels I didn't tried

Michal

             reply	other threads:[~2003-02-24 20:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 21:06 Michal Semler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-19  6:23 Can't compile Boris de Laage
2005-05-19  6:23 ` phil
2005-05-19  6:23 ` Mark D. Studebaker
2005-02-01 10:50 can't compile zhiyi6
     [not found] <1032676882.752.116.camel@zen8100a>
2002-09-22 23:00 ` Zenaan Harkness
2002-09-23 13:10   ` Frans Ketelaars
2002-09-23 23:43     ` Zenaan Harkness

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=E18nPoV-0000XD-00@notas \
    --to=cijoml@volny.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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.