From: Khem Raj <raj.khem@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 18:32:48 -0700 [thread overview]
Message-ID: <20100402013248.GB6161@gmail.com> (raw)
In-Reply-To: <20100401182116.GA27613@mx.loc>
On (01/04/10 20:21), Bernhard Reutner-Fischer wrote:
> 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..
While this is certainly possible, I am not in favor of using wildcards in
this case because, its more explicit on what we want to strip and it also
can tell us problems if a given .so was not built for some reason where we
expected it to.
>
> > Is this the correct fix or should libstdc++
> >already exist?
> >
> >Related Commit: 8c4198fc
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2010-04-02 1:35 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
2010-04-01 23:45 ` Ryan Phillips
2010-04-02 1:32 ` Khem Raj [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=20100402013248.GB6161@gmail.com \
--to=raj.khem@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