All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: RFC: SDK/external-toolchain fixes
Date: Thu, 11 Sep 2008 15:52:43 -0400	[thread overview]
Message-ID: <20080911195243.GA16359@denix.org> (raw)

Hi,

I've been playing with OE's SDK and external-toolchain features lately and
stumbled upon couple of issues. Thanks to Philip Balister for commiting
trivial fixes in, now I have 2 more, which require wider review. Please let
me know of any problems or comments. Thanks.


#1 gcc-cross-sdk 4.3.1 missing include-fixed
http://bugs.openembedded.net/show_bug.cgi?id=4536

gcc 4.3.x has some GCC-provided headers in include-fixed (namely limits.h),
which are missing in the gcc-cross-sdk version, rendering external toolchain
unusable.

Provided patch copies them in the include directory as a temporary solution.
A similar temporary solution is present in gcc-cross_4.3.1, see
do_stage_append()


#2 external-toolchain misses providing runtime libgcc
http://bugs.openembedded.net/show_bug.cgi?id=4542

Since external-toolchain misses specifying libgcc as provided runtime library,
dependency tree picks up either gcc-cross or even gcc-noemu...

Attached patch fixes the problem.


-- 
Denys



             reply	other threads:[~2008-09-11 19:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-11 19:52 Denys Dmytriyenko [this message]
2008-09-12  0:02 ` RFC: SDK/external-toolchain fixes Khem Raj
2008-09-12  1:53   ` Denys Dmytriyenko
2008-09-12  2:11     ` Khem Raj
2008-09-12  7:40       ` Denys Dmytriyenko
2008-09-13 13:49       ` Koen Kooi
2008-09-13 19:06         ` Khem Raj
2008-09-13 19:34           ` Koen Kooi
2008-09-15  7:18           ` Denys Dmytriyenko
2008-09-19 21:01             ` Denys Dmytriyenko
2008-09-23 17:16               ` Denys Dmytriyenko
2008-09-23 18:44                 ` Khem Raj

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=20080911195243.GA16359@denix.org \
    --to=denis@denix.org \
    --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 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.