From: Wolfgang Denk <wd@denx.de>
To: "Mathews, Phil" <Phil.Mathews@innocon.com>
Cc: Linuxppc-embedded@ozlabs.org
Subject: Re: Unable to build ELDK 4.0
Date: Thu, 31 Aug 2006 22:00:26 +0200 [thread overview]
Message-ID: <20060831200026.60FA5352640@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 31 Aug 2006 12:13:11 EDT." <3E8081396F6B524BA2854E7FA3F16438042EB1DF@mail.innocon.com>
In message <3E8081396F6B524BA2854E7FA3F16438042EB1DF@mail.innocon.com> you wrote:
>
> mathews@mathews:~/ELDK/ppc_6xx/usr/src/linux-2.6.15> make O=/home/name/build/kernel menuconfig
> HOSTCC scripts/basic/fixdep
> In file included from /home/mathews/ELDK/usr/../ppc_6xx/usr/include/sys/socket.h:35,
> from /home/mathews/ELDK/usr/../ppc_6xx/usr/include/netinet/in.h:24,
> from /home/mathews/ELDK/usr/../ppc_6xx/usr/include/arpa/inet.h:23,
> from /home/mathews/ELDK/ppc_6xx/usr/src/linux-2.6.15/scripts/basic/fixdep.c:115:
> /home/mathews/ELDK/usr/../ppc_6xx/usr/include/bits/socket.h:304:24: error: asm/socket.h: No such file or directory
> make[2]: *** [scripts/basic/fixdep] Error 1
> make[1]: *** [scripts_basic] Error 2
> make: *** [menuconfig] Error 2
It's working fine here. Did you install from CDROM or from a down-
load? Did you verify the downloaded files? Were there any error
messages dureing installation? Did you try a fresh reinstall?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
I used to be indecisive, now I'm not sure.
prev parent reply other threads:[~2006-08-31 20:00 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 ` Unable to build ELDK 4.0 Mathews, Phil
2006-08-31 15:58 ` Wolfgang Denk
2006-08-31 16:13 ` Mathews, Phil
2006-08-31 20:00 ` Wolfgang Denk [this message]
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=20060831200026.60FA5352640@atlas.denx.de \
--to=wd@denx.de \
--cc=Linuxppc-embedded@ozlabs.org \
--cc=Phil.Mathews@innocon.com \
/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