linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: fabien <fabien.fb@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: cant' compile busybox-1.8.1 with eldk 4.1
Date: Fri, 23 Nov 2007 11:56:23 +0100	[thread overview]
Message-ID: <f8f856500711230256j5f3c7b9fneb7351a4fdfdfe09@mail.gmail.com> (raw)

I try to compile busybox for my ppc custom  board. I successfuly
compile kernel 2.6.19 with
eldk and boot it. Now i try to get busybox working but i get some
errors at compile time.
It's look strange if someone can spend one minute to look at the compile log
What step could i miss ?
Thank a lot

[fabien@localhost busybox-1.8.1]  cat /opt/eldk/version
ELDK version 4.1
ppc_8xx: Build 2007-01-21-uclibc

[fabien@localhost busybox-1.8.1]$ make CROSS_COMPILE=ppc_8xx-
 CC      applets/applets.o
In file included from /opt/eldk/usr/../ppc_8xx/usr/include/netinet/in.h:212,
                from /opt/eldk/usr/../ppc_8xx/usr/include/arpa/inet.h:23,
                from include/platform.h:139,
                from include/libbb.h:13,
                from include/busybox.h:10,
                from applets/applets.c:11:
/opt/eldk/usr/../ppc_8xx/usr/include/bits/socket.h:305:24: error:
asm/socket.h: No such file or directory
In file included from /opt/eldk/usr/../ppc_8xx/usr/include/sys/ioctl.h:27,
                from /opt/eldk/usr/../ppc_8xx/usr/include/sys/mount.h:26,
                from include/platform.h:305,
                from include/libbb.h:13,
                from include/busybox.h:10,
                from applets/applets.c:11:
/opt/eldk/usr/../ppc_8xx/usr/include/bits/ioctls.h:24:24: error:
asm/ioctls.h: No such file or directory
In file included from /opt/eldk/usr/../ppc_8xx/usr/include/signal.h:309,
                from include/libbb.h:23,
                from include/busybox.h:10,
                from applets/applets.c:11:
/opt/eldk/usr/../ppc_8xx/usr/include/bits/sigcontext.h:28:29: error:
asm/sigcontext.h: No such file or directory
In file included from /opt/eldk/usr/../ppc_8xx/usr/include/ucontext.h:25,
                from /opt/eldk/usr/../ppc_8xx/usr/include/signal.h:326,
                from include/libbb.h:23,
                from include/busybox.h:10,
                from applets/applets.c:11:
/opt/eldk/usr/../ppc_8xx/usr/include/sys/ucontext.h:37: error: field
'uc_mcontext' has incomplete type
In file included from /opt/eldk/usr/../ppc_8xx/usr/include/sys/param.h:24,
                from include/libbb.h:67,
                from include/busybox.h:10,
                from applets/applets.c:11:
/opt/eldk/usr/../ppc_8xx/usr/include/linux/param.h:4:23: error:
asm/param.h: No such file or directory
make[1]: *** [applets/applets.o] Erreur 1
make: *** [applets] Erreur 2

             reply	other threads:[~2007-11-23 10:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-23 10:56 fabien [this message]
2007-11-23 12:05 ` cant' compile busybox-1.8.1 with eldk 4.1 Clemens Koller
2007-11-23 12:39   ` fabien
2007-11-23 14:48     ` Wolfgang Denk
2007-11-23 15:08       ` fabien

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=f8f856500711230256j5f3c7b9fneb7351a4fdfdfe09@mail.gmail.com \
    --to=fabien.fb@gmail.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;
as well as URLs for NNTP newsgroup(s).