From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] libunwind: force gcc to be built first
Date: Thu, 30 Sep 2010 10:49:07 +0200 [thread overview]
Message-ID: <4CA44F03.2020109@dresearch.de> (raw)
In-Reply-To: <1285777033-19478-1-git-send-email-t.fromm@dresearch.de>
Am 29.09.2010 18:17, schrieb Thilo Fromm:
> libunwind causes cross gcc build to fail if libunwind is built first:
> ...
> This patch makes libunwind depend on gcc which resolves the build issue. Both
> build nicely when gcc is built first.
>
> Signed-off-by: Thilo Fromm <t.fromm@dresearch.de>
Acked-by: Steffen Sledz <sledz@dresearch.de>
--
Steffen Sledz
DResearch Digital Media Systems GmbH
Otto-Schmirgal-Str.3, D-10319 Berlin, Germany
Tel: +49 (30) 515932237 mailto:sledz@DResearch.DE
Fax: +49 (30) 515932299 http://www.DResearch.DE
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 54412;
Ust.-IDNr. DE169013825; WEEE Reg.-Nr. DE 85995642
next prev parent reply other threads:[~2010-09-30 8:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 16:17 [PATCH] libunwind: force gcc to be built first Thilo Fromm
2010-09-30 8:49 ` Steffen Sledz [this message]
2010-09-30 10:21 ` Frans Meulenbroeks
2010-09-30 10:47 ` Thilo Fromm
2010-09-30 11:30 ` Frans Meulenbroeks
2010-10-01 10:09 ` Thilo Fromm
2010-10-01 17:16 ` Khem Raj
2010-10-02 6:33 ` Frans Meulenbroeks
2010-10-04 8:08 ` Thilo Fromm
2010-10-04 16:00 ` Khem Raj
2011-02-14 8:32 ` Steffen Sledz
2011-02-14 17:27 ` Tom Rini
2011-02-14 17:58 ` Khem Raj
2011-02-14 19:10 ` Sledz, Steffen
2011-02-25 8:51 ` Steffen Sledz
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=4CA44F03.2020109@dresearch.de \
--to=sledz@dresearch.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