From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: gcc QA issue
Date: Sat, 11 Dec 2010 03:04:02 -0800 [thread overview]
Message-ID: <20101211110402.GC10409@gmail.com> (raw)
In-Reply-To: <AANLkTimi=FMoZrm_Yum8xLkUkwd5+aYXDjguAqHj3mQS@mail.gmail.com>
On (08/12/10 09:18), Frans Meulenbroeks wrote:
> We bumped intot he following gcc QA issue (distro angsgtrom, machine
> mpc8313e-rdb)
>
> ERROR: QA Issue with gcc: non -dev package contains symlink .so: gcc
> path '/work/ppce300c3-angstrom-linux/gcc-4.3.3-r20.1/packages-split/gcc/usr/lib/gcc/powerpc-angstrom-linux/4.3.3/libgcc_s.so'
> NOTE: package objc skipped
> NOTE: package gcc-4.3.3-r20.1: task do_package: Succeeded
>
> Anyone a suggestion?
Do you still see this after my latest fixes to gcc ?
>
> Frans
>
> _______________________________________________
> 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-12-11 11:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 8:18 gcc QA issue Frans Meulenbroeks
2010-12-11 11:04 ` 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=20101211110402.GC10409@gmail.com \
--to=raj.khem@gmail.com \
--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