From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-users@linuxtogo.org
Subject: Re: error building meta-toolchain for powerpc 405
Date: Thu, 1 Apr 2010 20:21:16 +0200 [thread overview]
Message-ID: <20100401182116.GA27613@mx.loc> (raw)
In-Reply-To: <p2k46a47f951004010909sfb05675bx2ad6274204621bd6@mail.gmail.com>
On Thu, Apr 01, 2010 at 11:09:56AM -0500, Ryan Phillips wrote:
>Patch attached... It looks like gcc-package-sdk needs to have the
>strips be optional.
Apart from the question below, why not just invoke strip once for all of
them?
${TARGET_PREFIX}strip ${D}${prefix}/${TARGET_SYS}/lib/*.so.* || :
just curious..
> Is this the correct fix or should libstdc++
>already exist?
>
>Related Commit: 8c4198fc
next prev parent reply other threads:[~2010-04-01 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <t2n46a47f951003312246y97e7b196m59c6d8136580adb0@mail.gmail.com>
2010-04-01 16:09 ` error building meta-toolchain for powerpc 405 Ryan Phillips
2010-04-01 18:21 ` Bernhard Reutner-Fischer [this message]
2010-04-01 23:45 ` Ryan Phillips
2010-04-02 1:32 ` 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=20100401182116.GA27613@mx.loc \
--to=rep.dot.nop@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-users@linuxtogo.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