Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: empty dirs in glib-2.0
Date: Sat, 25 Feb 2012 14:55:16 +0000	[thread overview]
Message-ID: <1330181716.13788.33.camel@ted> (raw)
In-Reply-To: <17057774.C0TjevbrGC@kgy>

On Sat, 2012-02-25 at 13:26 +0100, Kövesdi György wrote:
> Hi,
> 
> Compiling the Angstrom Linux, in the file openembedded-core/meta/recipes-
> core/glib-2.0/glib-2.0_2.30.2.bb (a85f283ffae5407b23532ce2262142ee2d986af2) 
> there are the followings:
> 
> do_install_append() {
>   # remove some unpackaged files
>   rm -f ${D}${libdir}/gdbus-2.0/codegen/*.pyc
>   rm -f ${D}${libdir}/gdbus-2.0/codegen/*.pyo
>   # and empty dirs
>   rmdir ${D}${libdir}/gio/modules/
>   rmdir ${D}${libdir}/gio/
> }
> 
> I have problems with the "empty dirs" section: the directory is not empty and 
> therefore the installation fails here.
> I replaced it with "rm -rf ..." and now it worx but i do not sure it is a good 
> solution.
> Why these directories are expected to be empty? What does it mean if they are 
> not?

rmdir was used specifically so we'd know if the directory wasn't empty.
What files are in there?

Are there any .bbappends to the glib recipe in any of your other layers?

Cheers,

Richard




  reply	other threads:[~2012-02-25 15:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-25 12:26 empty dirs in glib-2.0 Kövesdi György
2012-02-25 14:55 ` Richard Purdie [this message]
2012-02-27 10:30   ` Gyorgy Kovesdi
2012-02-27 10:41     ` Jack Mitchell
2012-02-27 11:05       ` Ni Qingliang
2012-02-27 12:08         ` Andrea Adami
2012-02-27 12:17         ` Richard Purdie
2012-02-27 10:44     ` Gyorgy Kovesdi

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=1330181716.13788.33.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@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