Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On Thu, Apr 25, 2013 at 7:12 AM, Phil Blundell p...@pbcl.net wrote:
Something like IMAGE_FEATURES += dbg-pkgs should trigger the addition
of dbg packages.
I've somewhat belatedly gotten around to using this and encountered a
couple of issuettes:
1. There was a spurious-looking RRECOMMENDS_${PN}-dbg in bitbake.conf
which was causing ${PN} to be dragged into the image whenever ${PN}-dbg
was installed. This is undesirable because it means that, for example,
any image which includes sysvinit-pidof will end up installing sysvinit
and this might cause quite drastic changes to the behaviour of the
resulting image.
2. Having fixed the above I'm now left with a couple of file conflicts
in the -dbg packages. For example, sysvinit and util-linux both
ship /sbin/sulogin and so sysvinit-dbg and util-linux-dbg both want to
install /sbin/.debug/sulogin. This is unfortunate if you have an image
which uses, say, sysvinit-pidof and util-linux-blkid.
I'm not quite sure what the right way to fix (2) is. I suppose in an
ideal world the -dbg packages would be separated in the same way the
parent binary packages are, but that doesn't look entirely
straightforward to arrange.
I had implemented something along these lines back in oe classic, when I
was at MontaVista. See
http://git.openembedded.org/openembedded/tree/classes/package_dbg.bbclass for
that implementation. I haven't touched it or tried using it in some time,
however.
--
Christopher Larson
clarson at kergoth dot com
Senior Software Engineer, Mentor Graphics
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On Thu, 2013-04-25 at 08:47 -0500, Mark Hatle wrote: Is this a problem that they should have used the update-alternatives for sulogin? (Sounds like it might be a security issue though...) This would avoid the .debug conflict. I dunno. It seems a bit sad to force use of update-alternatives just to deconflict the .debug data (since the binaries in question would never be installed at the same time anyway), and in general it seems like we want less update-alternatives rather than more of it. But I guess that would indeed solve the problem and it's probably the lowest-effort thing that does. So maybe that's the way ahead. p. ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On 4/26/13 8:57 AM, Phil Blundell wrote: On Thu, 2013-04-25 at 08:47 -0500, Mark Hatle wrote: Is this a problem that they should have used the update-alternatives for sulogin? (Sounds like it might be a security issue though...) This would avoid the .debug conflict. I dunno. It seems a bit sad to force use of update-alternatives just to deconflict the .debug data (since the binaries in question would never be installed at the same time anyway), and in general it seems like we want less update-alternatives rather than more of it. But I guess that would indeed solve the problem and it's probably the lowest-effort thing that does. So maybe that's the way ahead. The alternative of course is to crease special -dbg packages for the two conflicting items. I.e. foo-dbg, foo-sulogin-dbg, bar-dbg and bar-sulogin-dbg... --Mark p. ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On Fri, 2013-04-26 at 09:16 -0500, Mark Hatle wrote: The alternative of course is to crease special -dbg packages for the two conflicting items. I.e. foo-dbg, foo-sulogin-dbg, bar-dbg and bar-sulogin-dbg... Yeah, indeed, that's what I suggested in my original email. At the time I thought that would be hard to arrange (in the general case), but having given it some further consideration perhaps it isn't all that bad after all. p. ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On 4/26/13 9:27 AM, Phil Blundell wrote: On Fri, 2013-04-26 at 09:16 -0500, Mark Hatle wrote: The alternative of course is to crease special -dbg packages for the two conflicting items. I.e. foo-dbg, foo-sulogin-dbg, bar-dbg and bar-sulogin-dbg... Yeah, indeed, that's what I suggested in my original email. At the time I thought that would be hard to arrange (in the general case), but having given it some further consideration perhaps it isn't all that bad after all. I certainly wouldn't be against an enhancement that tries to match up the binaries to their debug and create suitably named -dbg packages. The only tricky part is what to do with the associated sources? Since those are not arranged according to binaries, but generally for the whole recipe. --Mark p. ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On Fri, 2013-04-26 at 09:39 -0500, Mark Hatle wrote:
On 4/26/13 9:27 AM, Phil Blundell wrote:
On Fri, 2013-04-26 at 09:16 -0500, Mark Hatle wrote:
The alternative of course is to crease special -dbg packages for the two
conflicting items. I.e. foo-dbg, foo-sulogin-dbg, bar-dbg and
bar-sulogin-dbg...
Yeah, indeed, that's what I suggested in my original email. At the time
I thought that would be hard to arrange (in the general case), but
having given it some further consideration perhaps it isn't all that bad
after all.
I certainly wouldn't be against an enhancement that tries to match up the
binaries to their debug and create suitably named -dbg packages. The only
tricky part is what to do with the associated sources? Since those are not
arranged according to binaries, but generally for the whole recipe.
The sources can stay where they are, in ${PN}-dbg. There won't be any
conflict there because the installed files are already namespaced by
recipe.
p.
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On Fri, Apr 26, 2013 at 11:41 AM, Phil Blundell p...@pbcl.net wrote:
On Fri, 2013-04-26 at 09:39 -0500, Mark Hatle wrote:
On 4/26/13 9:27 AM, Phil Blundell wrote:
On Fri, 2013-04-26 at 09:16 -0500, Mark Hatle wrote:
The alternative of course is to crease special -dbg packages for the two
conflicting items. I.e. foo-dbg, foo-sulogin-dbg, bar-dbg and
bar-sulogin-dbg...
Yeah, indeed, that's what I suggested in my original email. At the time
I thought that would be hard to arrange (in the general case), but
having given it some further consideration perhaps it isn't all that bad
after all.
I certainly wouldn't be against an enhancement that tries to match up the
binaries to their debug and create suitably named -dbg packages. The only
tricky part is what to do with the associated sources? Since those are not
arranged according to binaries, but generally for the whole recipe.
The sources can stay where they are, in ${PN}-dbg. There won't be any
conflict there because the installed files are already namespaced by
recipe.
Maybe add a ${PN}-source with it? So any -dbg could rdepends on it?
--
Otavio Salvador O.S. Systems
E-mail: ota...@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On 4/26/13 9:50 AM, Otavio Salvador wrote:
On Fri, Apr 26, 2013 at 11:41 AM, Phil Blundell p...@pbcl.net wrote:
On Fri, 2013-04-26 at 09:39 -0500, Mark Hatle wrote:
On 4/26/13 9:27 AM, Phil Blundell wrote:
On Fri, 2013-04-26 at 09:16 -0500, Mark Hatle wrote:
The alternative of course is to crease special -dbg packages for the two
conflicting items. I.e. foo-dbg, foo-sulogin-dbg, bar-dbg and
bar-sulogin-dbg...
Yeah, indeed, that's what I suggested in my original email. At the time
I thought that would be hard to arrange (in the general case), but
having given it some further consideration perhaps it isn't all that bad
after all.
I certainly wouldn't be against an enhancement that tries to match up the
binaries to their debug and create suitably named -dbg packages. The only
tricky part is what to do with the associated sources? Since those are not
arranged according to binaries, but generally for the whole recipe.
The sources can stay where they are, in ${PN}-dbg. There won't be any
conflict there because the installed files are already namespaced by
recipe.
Maybe add a ${PN}-source with it? So any -dbg could rdepends on it?
-dbg-source would be better.. but I don't mind that. I know there have been
complaints where people want the debug symbols on the target, but don't want the
debug sources. This could address that as well.
I'd suggest someone (Phil ?) collect these and add a open an enhancement bug in
the YP bugzilla. That way progress on implementation can be tracked. (Unless
of course someone just implements it.. but I'm guessing it won't be quite that
straightforward.)
--Mark
--
Otavio Salvador O.S. Systems
E-mail: ota...@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On Tue, 2012-10-02 at 12:38 +0100, Richard Purdie wrote:
On Tue, 2012-10-02 at 12:15 +0100, Phil Blundell wrote:
On Tue, 2012-10-02 at 12:12 +0100, Richard Purdie wrote:
Hasn't Paul added a general mechanism for doing this so we could add
this feature a level higher so that it could be used by all packaging
formats?
Ah, possibly. I'll have a look. Can you give me a pointer to the
mechanism you were thinking of?
Something like IMAGE_FEATURES += dbg-pkgs should trigger the addition
of dbg packages.
I've somewhat belatedly gotten around to using this and encountered a
couple of issuettes:
1. There was a spurious-looking RRECOMMENDS_${PN}-dbg in bitbake.conf
which was causing ${PN} to be dragged into the image whenever ${PN}-dbg
was installed. This is undesirable because it means that, for example,
any image which includes sysvinit-pidof will end up installing sysvinit
and this might cause quite drastic changes to the behaviour of the
resulting image.
2. Having fixed the above I'm now left with a couple of file conflicts
in the -dbg packages. For example, sysvinit and util-linux both
ship /sbin/sulogin and so sysvinit-dbg and util-linux-dbg both want to
install /sbin/.debug/sulogin. This is unfortunate if you have an image
which uses, say, sysvinit-pidof and util-linux-blkid.
I'm not quite sure what the right way to fix (2) is. I suppose in an
ideal world the -dbg packages would be separated in the same way the
parent binary packages are, but that doesn't look entirely
straightforward to arrange.
p.
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On Thu, Apr 25, 2013 at 12:12:54PM +0100, Phil Blundell wrote:
On Tue, 2012-10-02 at 12:38 +0100, Richard Purdie wrote:
On Tue, 2012-10-02 at 12:15 +0100, Phil Blundell wrote:
On Tue, 2012-10-02 at 12:12 +0100, Richard Purdie wrote:
Hasn't Paul added a general mechanism for doing this so we could add
this feature a level higher so that it could be used by all packaging
formats?
Ah, possibly. I'll have a look. Can you give me a pointer to the
mechanism you were thinking of?
Something like IMAGE_FEATURES += dbg-pkgs should trigger the addition
of dbg packages.
I've somewhat belatedly gotten around to using this and encountered a
couple of issuettes:
1. There was a spurious-looking RRECOMMENDS_${PN}-dbg in bitbake.conf
which was causing ${PN} to be dragged into the image whenever ${PN}-dbg
was installed. This is undesirable because it means that, for example,
any image which includes sysvinit-pidof will end up installing sysvinit
and this might cause quite drastic changes to the behaviour of the
resulting image.
2. Having fixed the above I'm now left with a couple of file conflicts
in the -dbg packages. For example, sysvinit and util-linux both
ship /sbin/sulogin and so sysvinit-dbg and util-linux-dbg both want to
install /sbin/.debug/sulogin. This is unfortunate if you have an image
which uses, say, sysvinit-pidof and util-linux-blkid.
I'm not quite sure what the right way to fix (2) is. I suppose in an
ideal world the -dbg packages would be separated in the same way the
parent binary packages are, but that doesn't look entirely
straightforward to arrange.
yes there is a lot of conflicts between PN-doc and PN-dbg, I had similar
issues when trying to build world-image:
http://lists.linuxtogo.org/pipermail/openembedded-core/2013-January/034744.html
--
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
signature.asc
Description: Digital signature
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On 4/25/13 6:12 AM, Phil Blundell wrote:
On Tue, 2012-10-02 at 12:38 +0100, Richard Purdie wrote:
On Tue, 2012-10-02 at 12:15 +0100, Phil Blundell wrote:
On Tue, 2012-10-02 at 12:12 +0100, Richard Purdie wrote:
Hasn't Paul added a general mechanism for doing this so we could add
this feature a level higher so that it could be used by all packaging
formats?
Ah, possibly. I'll have a look. Can you give me a pointer to the
mechanism you were thinking of?
Something like IMAGE_FEATURES += dbg-pkgs should trigger the addition
of dbg packages.
I've somewhat belatedly gotten around to using this and encountered a
couple of issuettes:
1. There was a spurious-looking RRECOMMENDS_${PN}-dbg in bitbake.conf
which was causing ${PN} to be dragged into the image whenever ${PN}-dbg
was installed. This is undesirable because it means that, for example,
any image which includes sysvinit-pidof will end up installing sysvinit
and this might cause quite drastic changes to the behaviour of the
resulting image.
2. Having fixed the above I'm now left with a couple of file conflicts
in the -dbg packages. For example, sysvinit and util-linux both
ship /sbin/sulogin and so sysvinit-dbg and util-linux-dbg both want to
install /sbin/.debug/sulogin. This is unfortunate if you have an image
which uses, say, sysvinit-pidof and util-linux-blkid.
Is this a problem that they should have used the update-alternatives for
sulogin? (Sounds like it might be a security issue though...) This would avoid
the .debug conflict.
--Mark
I'm not quite sure what the right way to fix (2) is. I suppose in an
ideal world the -dbg packages would be separated in the same way the
parent binary packages are, but that doesn't look entirely
straightforward to arrange.
p.
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
If ${IMAGE_BUILD_DEBUG} is set, construct a parallel tree containing
the debug data for the packages that have been installed in the
rootfs, then tar it up and deploy it alongside the rootfs images.
Signed-off-by: Phil Blundell ph...@gnu.org
---
meta/classes/image.bbclass |9 +
meta/classes/rootfs_ipk.bbclass | 15 +++
meta/conf/bitbake.conf |1 +
3 files changed, 25 insertions(+)
diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index ab212b3..c82fba1 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -445,3 +445,12 @@ do_package_write_deb[noexec] = 1
do_package_write_rpm[noexec] = 1
addtask rootfs before do_build
+
+fakeroot do_capture_debug() {
+ if [ ${IMAGE_BUILD_DEBUG} = 1 -a -n ${IMAGE_ROOTFS_DBG} -a -d
${IMAGE_ROOTFS_DBG} ]; then
+ tar czf ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.debug.tar.gz -C
${IMAGE_ROOTFS_DBG} .
+ [ ${IMAGE_NAME} == ${IMAGE_LINK_NAME} ] || ln -sf
${IMAGE_NAME}.debug.tar.gz ${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.debug.tar.gz
+ fi
+}
+
+addtask capture_debug before do_build after do_rootfs
diff --git a/meta/classes/rootfs_ipk.bbclass b/meta/classes/rootfs_ipk.bbclass
index 46e8d60..e4e74dd 100644
--- a/meta/classes/rootfs_ipk.bbclass
+++ b/meta/classes/rootfs_ipk.bbclass
@@ -9,6 +9,8 @@ EXTRAOPKGCONFIG ?=
ROOTFS_PKGMANAGE = opkg opkg-collateral ${EXTRAOPKGCONFIG}
ROOTFS_PKGMANAGE_BOOTSTRAP = run-postinsts
+IMAGE_BUILD_DEBUG ?= 0
+
do_rootfs[depends] += opkg-native:do_populate_sysroot
opkg-utils-native:do_populate_sysroot
do_rootfs[recrdeptask] += do_package_write_ipk
@@ -17,6 +19,7 @@ do_rootfs[lockfiles] += ${WORKDIR}/ipk.lock
IPKG_ARGS = -f ${IPKGCONF_TARGET} -o ${IMAGE_ROOTFS} --force-overwrite
# The _POST version also works when constructing the matching SDK
IPKG_ARGS_POST = -f ${IPKGCONF_TARGET} -o $INSTALL_ROOTFS_IPK
--force-overwrite
+IPKG_ARGS_DBG = -f ${IPKGCONF_TARGET} -o ${IMAGE_ROOTFS_DBG}
--force-overwrite
OPKG_PREPROCESS_COMMANDS = package_update_index_ipk;
package_generate_ipkg_conf
@@ -88,6 +91,18 @@ fakeroot rootfs_ipk_do_rootfs () {
fi
fi
+ if [ ${IMAGE_BUILD_DEBUG} = 1 -a -n ${IMAGE_ROOTFS_DBG} ]; then
+ all_pkgs=`opkg-cl ${IPKG_ARGS} list-installed | awk '{ print $1
}'`
+ [ ${IMAGE_ROOTFS_DBG} -ef ${IMAGE_ROOTFS} ] || rm -rf
${IMAGE_ROOTFS_DBG}
+ mkdir -p ${IMAGE_ROOTFS_DBG}${opkglibdir}
+ opkg-cl ${IPKG_ARGS_DBG} update
+ for p in $all_pkgs; do
+ if [ `opkg-cl ${IPKG_ARGS_DBG} info $p-dbg` != ];
then
+ opkg-cl ${IPKG_ARGS_DBG} --nodeps install $p-dbg
+ fi
+ done
+ fi
+
install -d ${IMAGE_ROOTFS}/${sysconfdir}
echo ${BUILDNAME} ${IMAGE_ROOTFS}/${sysconfdir}/version
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 87351e0..66152fe 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -399,6 +399,7 @@ STAGING_KERNEL_DIR = ${STAGING_DIR_HOST}/usr/src/kernel
##
IMAGE_ROOTFS = ${WORKDIR}/rootfs
+IMAGE_ROOTFS_DBG = ${IMAGE_ROOTFS}.debug
IMAGE_BASENAME = ${PN}
IMAGE_NAME = ${IMAGE_BASENAME}-${MACHINE}-${DATETIME}
IMAGE_LINK_NAME = ${IMAGE_BASENAME}-${MACHINE}
--
1.7.10.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On Tue, 2012-10-02 at 10:20 +0100, Phil Blundell wrote:
If ${IMAGE_BUILD_DEBUG} is set, construct a parallel tree containing
the debug data for the packages that have been installed in the
rootfs, then tar it up and deploy it alongside the rootfs images.
Signed-off-by: Phil Blundell ph...@gnu.org
---
meta/classes/image.bbclass |9 +
meta/classes/rootfs_ipk.bbclass | 15 +++
meta/conf/bitbake.conf |1 +
3 files changed, 25 insertions(+)
diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index ab212b3..c82fba1 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -445,3 +445,12 @@ do_package_write_deb[noexec] = 1
do_package_write_rpm[noexec] = 1
addtask rootfs before do_build
+
+fakeroot do_capture_debug() {
+ if [ ${IMAGE_BUILD_DEBUG} = 1 -a -n ${IMAGE_ROOTFS_DBG} -a -d
${IMAGE_ROOTFS_DBG} ]; then
+ tar czf ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.debug.tar.gz -C
${IMAGE_ROOTFS_DBG} .
+ [ ${IMAGE_NAME} == ${IMAGE_LINK_NAME} ] || ln -sf
${IMAGE_NAME}.debug.tar.gz ${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.debug.tar.gz
+ fi
+}
+
+addtask capture_debug before do_build after do_rootfs
diff --git a/meta/classes/rootfs_ipk.bbclass b/meta/classes/rootfs_ipk.bbclass
index 46e8d60..e4e74dd 100644
--- a/meta/classes/rootfs_ipk.bbclass
+++ b/meta/classes/rootfs_ipk.bbclass
@@ -9,6 +9,8 @@ EXTRAOPKGCONFIG ?=
ROOTFS_PKGMANAGE = opkg opkg-collateral ${EXTRAOPKGCONFIG}
ROOTFS_PKGMANAGE_BOOTSTRAP = run-postinsts
+IMAGE_BUILD_DEBUG ?= 0
+
do_rootfs[depends] += opkg-native:do_populate_sysroot
opkg-utils-native:do_populate_sysroot
do_rootfs[recrdeptask] += do_package_write_ipk
@@ -17,6 +19,7 @@ do_rootfs[lockfiles] += ${WORKDIR}/ipk.lock
IPKG_ARGS = -f ${IPKGCONF_TARGET} -o ${IMAGE_ROOTFS} --force-overwrite
# The _POST version also works when constructing the matching SDK
IPKG_ARGS_POST = -f ${IPKGCONF_TARGET} -o $INSTALL_ROOTFS_IPK
--force-overwrite
+IPKG_ARGS_DBG = -f ${IPKGCONF_TARGET} -o ${IMAGE_ROOTFS_DBG}
--force-overwrite
OPKG_PREPROCESS_COMMANDS = package_update_index_ipk;
package_generate_ipkg_conf
@@ -88,6 +91,18 @@ fakeroot rootfs_ipk_do_rootfs () {
fi
fi
+ if [ ${IMAGE_BUILD_DEBUG} = 1 -a -n ${IMAGE_ROOTFS_DBG} ]; then
+ all_pkgs=`opkg-cl ${IPKG_ARGS} list-installed | awk '{ print $1
}'`
+ [ ${IMAGE_ROOTFS_DBG} -ef ${IMAGE_ROOTFS} ] || rm -rf
${IMAGE_ROOTFS_DBG}
+ mkdir -p ${IMAGE_ROOTFS_DBG}${opkglibdir}
+ opkg-cl ${IPKG_ARGS_DBG} update
+ for p in $all_pkgs; do
+ if [ `opkg-cl ${IPKG_ARGS_DBG} info $p-dbg` != ];
then
+ opkg-cl ${IPKG_ARGS_DBG} --nodeps install $p-dbg
+ fi
+ done
+ fi
+
install -d ${IMAGE_ROOTFS}/${sysconfdir}
echo ${BUILDNAME} ${IMAGE_ROOTFS}/${sysconfdir}/version
Hasn't Paul added a general mechanism for doing this so we could add
this feature a level higher so that it could be used by all packaging
formats?
I'm a little concerned that the different backends are getting totally
different sets of features at this point. In some cases we have very
good reasons for it but that doesn't appear to be the case here.
Cheers,
Richard
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On Tue, 2012-10-02 at 12:12 +0100, Richard Purdie wrote: Hasn't Paul added a general mechanism for doing this so we could add this feature a level higher so that it could be used by all packaging formats? Ah, possibly. I'll have a look. Can you give me a pointer to the mechanism you were thinking of? thanks p. ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On Tue, 2012-10-02 at 12:15 +0100, Phil Blundell wrote: On Tue, 2012-10-02 at 12:12 +0100, Richard Purdie wrote: Hasn't Paul added a general mechanism for doing this so we could add this feature a level higher so that it could be used by all packaging formats? Ah, possibly. I'll have a look. Can you give me a pointer to the mechanism you were thinking of? Something like IMAGE_FEATURES += dbg-pkgs should trigger the addition of dbg packages. Cheers, Richard ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On Tue, Oct 2, 2012 at 8:38 AM, Richard Purdie richard.pur...@linuxfoundation.org wrote: On Tue, 2012-10-02 at 12:15 +0100, Phil Blundell wrote: On Tue, 2012-10-02 at 12:12 +0100, Richard Purdie wrote: Hasn't Paul added a general mechanism for doing this so we could add this feature a level higher so that it could be used by all packaging formats? Ah, possibly. I'll have a look. Can you give me a pointer to the mechanism you were thinking of? Something like IMAGE_FEATURES += dbg-pkgs should trigger the addition of dbg packages. Or IMAGE_FEATURES += dbg-img ;-) -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On Tue, 2012-10-02 at 12:38 +0100, Richard Purdie wrote: On Tue, 2012-10-02 at 12:15 +0100, Phil Blundell wrote: On Tue, 2012-10-02 at 12:12 +0100, Richard Purdie wrote: Hasn't Paul added a general mechanism for doing this so we could add this feature a level higher so that it could be used by all packaging formats? Ah, possibly. I'll have a look. Can you give me a pointer to the mechanism you were thinking of? Something like IMAGE_FEATURES += dbg-pkgs should trigger the addition of dbg packages. Ah yes, I see it. It looks like that will cause the debug packages to go into the rootfs itself, rather than a parallel tree, but I guess I can probably arrange to fish them back out again before the image is built. thanks p. ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On Tue, Oct 2, 2012 at 10:51 AM, Phil Blundell ph...@gnu.org wrote: On Tue, 2012-10-02 at 10:42 -0300, Otavio Salvador wrote: Or IMAGE_FEATURES += dbg-img ;-) Where is that implemented? I couldn't find any obvious reference to dbg-img in any classes. Sorry by cause a missunderstanding ... I was just pointing to a possible new feature you could add. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On 10/02/12 15:53, Otavio Salvador wrote: On Tue, Oct 2, 2012 at 10:51 AM, Phil Blundell ph...@gnu.org wrote: On Tue, 2012-10-02 at 10:42 -0300, Otavio Salvador wrote: Or IMAGE_FEATURES += dbg-img ;-) Where is that implemented? I couldn't find any obvious reference to dbg-img in any classes. Sorry by cause a missunderstanding ... I was just pointing to a possible new feature you could add. that feature is already implemented though, in dbg-pkgs. If you don't mean dbg-img should do something other/more than what dbg-pkgs does? - Martin ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On Tue, Oct 2, 2012 at 10:52 AM, Martin Ertsås mert...@cisco.com wrote: On 10/02/12 15:53, Otavio Salvador wrote: On Tue, Oct 2, 2012 at 10:51 AM, Phil Blundell ph...@gnu.org wrote: On Tue, 2012-10-02 at 10:42 -0300, Otavio Salvador wrote: Or IMAGE_FEATURES += dbg-img ;-) Where is that implemented? I couldn't find any obvious reference to dbg-img in any classes. Sorry by cause a missunderstanding ... I was just pointing to a possible new feature you could add. that feature is already implemented though, in dbg-pkgs. If you don't mean dbg-img should do something other/more than what dbg-pkgs does? To build a separated tar with the symbols, not on the image itself. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On 10/02/12 15:59, Otavio Salvador wrote: On Tue, Oct 2, 2012 at 10:52 AM, Martin Ertsås mert...@cisco.com wrote: On 10/02/12 15:53, Otavio Salvador wrote: On Tue, Oct 2, 2012 at 10:51 AM, Phil Blundell ph...@gnu.org wrote: On Tue, 2012-10-02 at 10:42 -0300, Otavio Salvador wrote: Or IMAGE_FEATURES += dbg-img ;-) Where is that implemented? I couldn't find any obvious reference to dbg-img in any classes. Sorry by cause a missunderstanding ... I was just pointing to a possible new feature you could add. that feature is already implemented though, in dbg-pkgs. If you don't mean dbg-img should do something other/more than what dbg-pkgs does? To build a separated tar with the symbols, not on the image itself. With only the symbols? Or a separate image with symbols, side by side with the stripped one? In the later case you could just add a export IMAGE_BASENAME = my-dbg-image in the image recipe. If you mean with only the symbols I don't think we have any features for that right now. - Martin ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] rootfs_ipk, image: Add debug capture support
On Tue, Oct 2, 2012 at 10:57 AM, Martin Ertsås mert...@cisco.com wrote: On 10/02/12 15:59, Otavio Salvador wrote: On Tue, Oct 2, 2012 at 10:52 AM, Martin Ertsås mert...@cisco.com wrote: On 10/02/12 15:53, Otavio Salvador wrote: On Tue, Oct 2, 2012 at 10:51 AM, Phil Blundell ph...@gnu.org wrote: On Tue, 2012-10-02 at 10:42 -0300, Otavio Salvador wrote: Or IMAGE_FEATURES += dbg-img ;-) Where is that implemented? I couldn't find any obvious reference to dbg-img in any classes. Sorry by cause a missunderstanding ... I was just pointing to a possible new feature you could add. that feature is already implemented though, in dbg-pkgs. If you don't mean dbg-img should do something other/more than what dbg-pkgs does? To build a separated tar with the symbols, not on the image itself. With only the symbols? Or a separate image with symbols, side by side with the stripped one? In the later case you could just add a export IMAGE_BASENAME = my-dbg-image in the image recipe. If you mean with only the symbols I don't think we have any features for that right now. I thought it being side by side. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
