All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Poky Project <poky@yoctoproject.org>
Subject: New warning
Date: Tue, 02 Oct 2012 09:34:27 -0600	[thread overview]
Message-ID: <506B0983.3060500@mlbassoc.com> (raw)

I'm getting these new warnings, even with a build from scratch.  This is from
poky master rev 7c39c87d52c20e47cf90275a16e4517a296c8388

WARNING: The recipe is trying to install files into a shared area when those files already exist. Those files are:
    /home/local/p81_build/tmp/sysroots/cobra3530p81/usr/include/python2.7/pyconfig.h
    /home/local/p81_build/tmp/sysroots/cobra3530p81/usr/lib/libpython2.7.so
    /home/local/p81_build/tmp/sysroots/cobra3530p81/usr/lib/libpython2.7.so.1.0
    /home/local/p81_build/tmp/sysroots/cobra3530p81/usr/lib/python2.7/config/Makefile

Do they hurt anything?  Why am I getting them now, what's changed, etc?

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


             reply	other threads:[~2012-10-02 15:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 15:34 Gary Thomas [this message]
2012-10-02 15:43 ` New warning Richard Purdie
2012-10-03  6:22   ` Khem Raj
  -- strict thread matches above, loose matches on Subject: below --
2016-06-08  2:55 Gary Thomas
2016-06-08  3:20 ` Christopher Larson
2012-06-20 19:12 Gary Thomas
2012-06-20 21:55 ` Khem Raj
2012-06-20 22:51   ` Gary Thomas
2012-06-21  8:26     ` Andrea Adami
2012-06-22  9:44     ` Paul Eggleton
2012-06-22 11:49       ` Gary Thomas
2012-06-22 12:35         ` Tomas Frydrych
2012-06-22 13:01         ` Paul Eggleton
2012-06-22 13:05           ` Paul Eggleton
2012-06-22 13:31             ` Gary Thomas
2012-06-22 14:25         ` 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=506B0983.3060500@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.