Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Nils Faerber <nils.faerber@kernelconcepts.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: ARM EABI SDK build
Date: Mon, 20 Nov 2006 12:26:02 +0100	[thread overview]
Message-ID: <456190CA.6000809@kernelconcepts.de> (raw)
In-Reply-To: <4559F05C.20003@kernelconcepts.de>

Hi!
I am made one step forward but do not think that it is the right way to
do it...
The task-sdk worked to build though meta-sdk still does not. Copying the
toolchain out of tmp/cross/ and adding libs from staging seems to work.

But it seems "unclean" to me and involves manual collection of all the
bits and pieces.

Still noone knows why meta-sdk fails?

Cheers
  nils

Nils Faerber schrieb:
> Koen Kooi schrieb:
>> Nils Faerber schreef:
>>>> OK, that was indeed fixed.
>>>> But I still have the problem that gcc-cross-sdk-4.1.1 fails to compile
>>>> due to problems with sys/types.h
>>>> This is really strange since this originates from glibc.
>>>>
>>>> Koen: Didn't you build an EABI-softfloat toolchain already?
>> Riku did:
>> http://dominion.kabel.utwente.nl/koen/cms/using-openembedded-toolchains-in-scratchbox
> 
> OK... well we tried both approaches now, the simpler one you mentioned
> on the list and our own - both failed at the same gcc-sdk compile in
> libiberty (see my previous log).
> 
> I now investigated this a little further..
> 
> First of all I think that gcc4-build-sdk.inc has an error. I think that
> line 3
> 
>   SRC_URI += 'file://602-sdk-libstdc++-includes.patch;patch=1'
> 
> is not needed (anymore) and rather causes do_patch to fail.
> After fixing that I get to the old point with libiberty, etc...
> 
> Then I tried to build gcc-cross target and see: It works!
> 
> So I suspect that there is some problem with the gcc-cross-sdk target.
> But I am too new to OE to be able to fix that, I fear.
> 
> So a big please to the maintainer of that target: Could you help me
> please? I need that compiler ;)
> 
> Many thanks!
> 
> Oh ... and please have someone review the above gcc4-build-sdk.inc and
> potentially remove the SRC_URI line...
> 
>> regards,
>> Koen
> Cheers
>   nils faerber

-- 
kernel concepts GbR      Tel: +49-271-771091-12
Dreisbachstr. 24         Fax: +49-271-771091-19
D-57250 Netphen          Mob: +49-176-21024535
--



      reply	other threads:[~2006-11-20 11:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-12  0:50 ARM EABI SDK build Nils Faerber
2006-11-13 12:54 ` Florian Boor
     [not found]   ` <45589A63.9030808@kernelconcepts.de>
2006-11-13 16:25     ` Marcin Juszkiewicz
2006-11-13 18:13       ` Nils Faerber
2006-11-13 20:50         ` Koen Kooi
2006-11-14 12:54           ` Nils Faerber
2006-11-14 13:07             ` Koen Kooi
2006-11-14 15:56               ` Richard Purdie
2006-11-14 16:35           ` Nils Faerber
2006-11-20 11:26             ` Nils Faerber [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=456190CA.6000809@kernelconcepts.de \
    --to=nils.faerber@kernelconcepts.de \
    --cc=openembedded-devel@lists.openembedded.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