LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Mathews, Phil" <Phil.Mathews@innocon.com>
To: <Linuxppc-embedded@ozlabs.org>
Subject: Unable to build ELDK 4.0
Date: Thu, 31 Aug 2006 11:18:42 -0400	[thread overview]
Message-ID: <3E8081396F6B524BA2854E7FA3F16438042EB1DB@mail.innocon.com> (raw)
In-Reply-To: 5df98b760608310618p746e1ee7q62b9472fa855660f@mail.gmail.com

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

I am attempting to build the ELDK kernel using the directions in /home/mathews/ELDK/ppc_6xx/usr/src/linux-2.6.15/README.  The makefile is trying to execute powerPC code (fixdep) on my Pentium box.  Where can I get a X86 version of this program?

##### Make attempt:
mathews@mathews:~/ELDK/ppc_6xx/usr/src/linux-2.6.15> make O=/home/name/build/kernel menuconfig
  HOSTCC  scripts/basic/fixdep
/bin/sh: scripts/basic/fixdep: cannot execute binary file
make[2]: *** [scripts/basic/fixdep] Error 126
make[1]: *** [scripts_basic] Error 2
make: *** [menuconfig] Error 2

##### Objdump of scripts/basic/fixdep
mathews@mathews:~/ELDK/ppc_6xx/usr/src/linux-2.6.15> objdump -a scripts/basic/fixdep

scripts/basic/fixdep:     file format elf32-powerpc
scripts/basic/fixdep

mathews@mathews:~/ELDK/ppc_6xx/usr/src/linux-2.6.15> echo $PATH
/home/mathews/ELDK/usr/bin:/home/mathews/ELDK/usr/ppc-linux/bin:/home/mathews/bin:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/games:/opt/gnome/bin:/opt/kde3/bin


--  Phil Mathews  
    phil.mathews _at_ innocon.com    

[-- Attachment #2: Type: text/html, Size: 1615 bytes --]

  reply	other threads:[~2006-08-31 15:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-31 13:18 watchdog on mpc8260 with embedded linux Wang LP
2006-08-31 15:18 ` Mathews, Phil [this message]
2006-08-31 15:58   ` Unable to build ELDK 4.0 Wolfgang Denk
2006-08-31 16:13     ` Mathews, Phil
2006-08-31 20:00       ` Wolfgang Denk

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=3E8081396F6B524BA2854E7FA3F16438042EB1DB@mail.innocon.com \
    --to=phil.mathews@innocon.com \
    --cc=Linuxppc-embedded@ozlabs.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