linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukasz Majewski <majess1982@gmail.com>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: [linux-2.6.26.8-rt14] RT Page Fault.
Date: Mon, 23 Feb 2009 17:21:36 +0100	[thread overview]
Message-ID: <49A2CD10.4080605@gmail.com> (raw)
In-Reply-To: <20090223124016.GH5367@pengutronix.de>

Hello Robert.

I'm building toolchain for AT572D940HF Atmel chip. It's ARM9 combined 
with DSP. I'd like to build toolchain for ARM9 (ARMv5tej) with 
-msoft-float support, EABI and full glibc ,to support all stuff 
connected with PREEMPT_RT patch - especially librt.

Now I've downloaded:
ptxdist-1.99.11 and ptxdist-1.99.11-patches.

and
OSELAS.Toolchain-1.99.3

I've selected 
./ptxconfigs/arm-v5te-linux-gnueabi-gcc-4.3.2-glibc-2.8-binutils-2.18-kernel-2.6.27-sanitized

I need toolchain with -msoft-float support and EABI.

Unfortunately there is an error about mismatch in the linux-kernel 
headers. My Host PC has linux-kernel of 2.6.24 and not 2.6.27. My target 
is working under 2.6.26.8-rt14 kernel.
The error is in building of NTPL library, after successfully compilation 
of gcc compiler.

How can I provide proper kernel headers?

Now I'm trying with 
arm-v5te-linux-gnueabi-gcc-4.1.2-glibc-2.5-binutils-2.17-kernel-2.6.18 
ptxconfig. I hope that this will be sufficiently new to provide priority 
inheritance, futexes , librt with all features.

I'm building it now and hope that I won't encounter any problems.


Regards,
Lukasz

Robert Schwebel wrote:
> On Mon, Feb 23, 2009 at 12:01:04AM +0100, Lukasz Majewski wrote:
>   
>> Now some explanation about uClibc. I know that this C library lacks of
>> many features (for instance NTPL support for ARM). Unfortunately, for
>> ARM architecture, there is nice utility -> buildroot  for building
>> toolchain and  root filesystems.
>>     
>
> You can use ptxdist do do almost the same.
>
>   
>> I've tried pxtdist tool from pengutronix.de, but I cannot build proper
>> toolchain without errors for my Atmel's ARM9 device (ARMv5tej arch to be
>> precise). Or saying it in another way -> I gave up after spending some
>> time and moved back toward working uClibc.
>>     
>
> Well, you could have reported that to the OSELAS.Toolchain maintainers :)
>
> What kind of problem do you see? We are using the the v5te toolchain
> quite intensively on AT91SAM9260 and AT91SAM9263 without problems.
>
> So send us your error output and let's see what we can do. The ptxdist
> mailing list is probably the right list for that kind of discussion.
>
> rsc
>   


  reply	other threads:[~2009-02-23 16:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-22 20:49 [linux-2.6.26.8-rt14] RT Page Fault Lukasz Majewski
2009-02-22 21:29 ` Remy Bohmer
2009-02-22 23:01   ` Lukasz Majewski
2009-02-23 10:12     ` Remy Bohmer
2009-02-23 12:40     ` Robert Schwebel
2009-02-23 16:21       ` Lukasz Majewski [this message]
2009-02-23 20:46         ` Robert Schwebel
2009-02-24  0:00           ` Lukasz Majewski

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=49A2CD10.4080605@gmail.com \
    --to=majess1982@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=r.schwebel@pengutronix.de \
    /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).