From: fabien <fabien.fb@gmail.com>
To: "Clemens Koller" <clemens.koller@anagramm.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: cant' compile busybox-1.8.1 with eldk 4.1
Date: Fri, 23 Nov 2007 13:39:59 +0100 [thread overview]
Message-ID: <f8f856500711230439q39c352ffi4cf3a206de68733a@mail.gmail.com> (raw)
In-Reply-To: <4746C1F6.9050601@anagramm.de>
Thanks Clemens i've opened a thread in busybox mailing list :
http://www.busybox.net/lists/busybox/2007-November/029322.html
2007/11/23, Clemens Koller <clemens.koller@anagramm.de>:
> fabien schrieb:
> > I try to compile busybox for my ppc custom board.
>
> What ARCH/cpu?
>
> > 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 compi=
le log
> > What step could i miss ?
>
> > [...]
> > /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
>
> It looks like your kernel headers (ARCH-specific or generic)
> are broken or missing.
> See i.e. Linux From Scratch to get an idea about the dependencies.
> Or, see latest kernel's 'make headers_install' target and how it is used.
> Google is your friend, here...
>
> The busybox mailing list would be more suited for this question.
>
> Regards,
>
> Clemens Koller
> __________________________________
> R&D Imaging Devices
> Anagramm GmbH
> Rupert-Mayer-Stra=DFe 45/1
> Linhof Werksgel=E4nde
> D-81379 M=FCnchen
> Tel.089-741518-50
> Fax 089-741518-19
> http://www.anagramm-technology.com
>
>
next prev parent reply other threads:[~2007-11-23 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 10:56 cant' compile busybox-1.8.1 with eldk 4.1 fabien
2007-11-23 12:05 ` Clemens Koller
2007-11-23 12:39 ` fabien [this message]
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=f8f856500711230439q39c352ffi4cf3a206de68733a@mail.gmail.com \
--to=fabien.fb@gmail.com \
--cc=clemens.koller@anagramm.de \
--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).