From: Robert Schuster <theBohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: QA Logs now on tinderbox
Date: Tue, 23 Sep 2008 11:34:39 +0200 [thread overview]
Message-ID: <48D8B82F.6010103@gmx.net> (raw)
In-Reply-To: <d1b08f940809230158s78f04a4bq866bf586dce5cafe@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 371 bytes --]
Hi,
is there a way to override this being reported as a problem in case of
these problems:
> non dev contains .so, gcc,
> /work/armv5teb-angstrom-linux-gnueabi/gcc-4.2.4-r3/install/gcc/usr/lib/gcc/armeb-angstrom-linux-gnueabi/4.2.4/libgcc_s.so
I ask because boost on purpose distributes lib*.so files and creates a
lot of binary packages.
Regards
Robert
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 268 bytes --]
next prev parent reply other threads:[~2008-09-23 9:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 8:58 QA Logs now on tinderbox Andrea Adami
2008-09-23 9:34 ` Robert Schuster [this message]
2008-09-23 11:14 ` Koen Kooi
2008-09-23 15:42 ` Andrea Adami
2008-09-23 15:54 ` Koen Kooi
2008-09-23 17:18 ` Jeremy Lainé
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=48D8B82F.6010103@gmx.net \
--to=thebohemian@gmx.net \
--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