From: Khem Raj <raj.khem@gmail.com>
To: Matteo Fortini <matteo.fortini@mta.it>
Cc: "openembedded-devel@openembedded.org"
<openembedded-devel@openembedded.org>
Subject: Re: nof/libgcc_s.so installed instead of libgcc_s.so on powerpc
Date: Fri, 26 Jun 2009 17:59:50 -0700 [thread overview]
Message-ID: <200906261759.56663.raj.khem@gmail.com> (raw)
In-Reply-To: <4A3A5A84.6090602@mta.it>
[-- Attachment #1: Type: Text/Plain, Size: 191 bytes --]
On Thursday 18 June 2009 08:17:24 am Matteo Fortini wrote:
> Here it is
Thanks. It might be problem in install section of our recipes.
Can you post log.do_compile file
Thx
-Khem
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 204 bytes --]
next prev parent reply other threads:[~2009-06-27 1:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 14:34 nof/libgcc_s.so installed instead of libgcc_s.so on powerpc Matteo Fortini
2009-06-15 15:03 ` Leon Woestenberg
2009-06-15 15:21 ` Matteo Fortini
2009-06-18 6:09 ` Khem Raj
2009-06-18 15:17 ` Matteo Fortini
2009-06-27 0:59 ` Khem Raj [this message]
2009-11-30 1:15 ` Jeremy Williams
2009-11-30 18:45 ` Khem Raj
2009-12-02 18:04 ` Jeremy Williams
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=200906261759.56663.raj.khem@gmail.com \
--to=raj.khem@gmail.com \
--cc=matteo.fortini@mta.it \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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