All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@domain.hid>
To: Peter Feuerer <peter.feuerer@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] ppc crosscompilation, missing headers
Date: Tue, 22 May 2007 15:52:13 +0200	[thread overview]
Message-ID: <4652F58D.2070305@domain.hid> (raw)
In-Reply-To: <1179838106.6050.46.camel@domain.hid>

Peter Feuerer wrote:
> Hi all,
> 
> I'm trying to crosscompile xenomai 2.3.1 for the ppc-architecture. 
> My commands are like this:  (using latest denx ELDK)
> 
> export ARCH=ppc
> export CROSS_COMPILE=ppc_8xx-
> 
> scripts/prepare-kernel.sh --arch=ppc
> --linux=/home/piie/toolchains/ppc-4.1/ppc_8xx/usr/src/linux/
> --adeos=ksrc/arch/powerpc/patches/adeos-ipipe-2.6.18-ppc-1.5-01.patch
> 
> cd bla/usr/src/linux/
> make TQM8260_defconfig

Hm, ppc_8xx is not the right tool-chain for this board. Please use 
ppc_6xx instead.

> make menuconfig
> make uImage
> 
> Everything is working so far and the kernel with built in xenomai boots
> flawless. (dmesg reports xenomai is working)
> 
> When trying to crosscompile the xenomai libs and so on, the configure
> step is working correctly.
> 
> ./configure -host=ppc-linux
> 
> But the make fails because of missing headers:
> [..]
>  error: asm/errno.h: No such file or directory
> [..]
>  error: asm/param.h: No such file or directory
> [..]
> 
> I took a look at the kernel/include/asm-ppc/ folder and actually these
> headers are missing. But they do exist for the "powerpc" architecture.
> So I just copied all missing headers from asm-powerpc/ to asm-ppc/ to
> try if the xenomai userspace things can be compiled. It worked. But I
> think that is not the way it has to be done.

Of course not and I'm also surprised that it fixed your problem.

> Does anybody know why these headers are missing in asm-ppc? Do I have to
> install some kind of BSP-kernel-patch for my specific board? Why are
> these headers available for powerpc?

No, when compiling for "ppc", the include files in "asm-powerpc" are 
included as well.

> And btw, maybe someone of you knows, why are there 2 architectures for
> the powerpc architecture in the kernel tree?

Traditionally, there was the "arch/ppc" tree for 32-bit PowerPC and 
"arch/ppc64" for 64-bit PowerPC. Both are merged already since a while 
into the new tree "arch/powerpc" ... and the old trees will become 
obsolete sooner than later.

Concerning your problem, I'm unable to reproduce it on my setup. What 
exact version of the ELDK do you use.

Wolfgang.



  reply	other threads:[~2007-05-22 13:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-22 12:48 [Xenomai-help] ppc crosscompilation, missing headers Peter Feuerer
2007-05-22 13:52 ` Wolfgang Grandegger [this message]
2007-05-22 14:41   ` Peter Feuerer
2007-05-22 14:52     ` Wolfgang Denk
2007-05-22 15:04       ` Peter Feuerer
2007-05-23  8:05       ` Peter Feuerer
2007-05-23  8:27         ` Wolfgang Grandegger
2007-05-23  8:27           ` Peter Feuerer
2007-05-23  9:09             ` Wolfgang Grandegger
2007-05-23  9:28               ` Peter Feuerer
2007-05-23  9:54                 ` Wolfgang Grandegger
2007-05-22 15:03     ` Wolfgang Grandegger

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=4652F58D.2070305@domain.hid \
    --to=wg@domain.hid \
    --cc=peter.feuerer@domain.hid \
    --cc=xenomai@xenomai.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 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.