From 38dc18977fc9babb161f90a83cf17441f79aafa3 Mon Sep 17 00:00:00 2001 From: Mike Westerhof Date: Mon, 31 Jul 2006 04:35:05 +0000 Subject: [PATCH] Unslung image: clean up .dbg files left by changed RUNSTRIP functionality --- packages/images/unslung-image.bb | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/packages/images/unslung-image.bb b/packages/images/unslung-image.bb index e57960ecdb..4d7958741c 100644 --- a/packages/images/unslung-image.bb +++ b/packages/images/unslung-image.bb @@ -1,5 +1,5 @@ LICENSE = MIT -PR = "r17" +PR = "r18" IMAGE_BASENAME = "unslung" @@ -80,6 +80,21 @@ unslung_clean_image () { rm -f ${IMAGE_ROOTFS}/usr/bin/locate rm -f ${IMAGE_ROOTFS}/usr/bin/updatedb rm -f ${IMAGE_ROOTFS}/usr/bin/xargs + + # FIXME: change made 24 Jul 2006 by the OE folks changes the "strip" + # behavior to create an extra file named .dbg containing + # the stripped symbols. These dbg files are supposed to be packaged + # separately by the standard bb routines, but for some reason this + # does not alway occur. This extremely ugly step is to remove the + # dbg cruft from the rootfs if any are left in the obvious locations. + # Once someone figures out why and what the right way is to fix this, + # this code should be removed. + + rm -f ${IMAGE_ROOTFS}/bin/*.dbg + rm -f ${IMAGE_ROOTFS}/sbin/*.dbg + rm -f ${IMAGE_ROOTFS}/usr/bin/*.dbg + rm -f ${IMAGE_ROOTFS}/usr/sbin/*.dbg + rm -f ${IMAGE_ROOTFS}/lib/*.dbg } python () { -- 2.39.5