apr: add libtool to SSTATE_SCAN_FILES
PATCH 1/1 apr: add libtool to SSTATE_SCAN_FILES
From: Jackie Huang <[email protected]>
The hardcoded paths in libtool will cause apache2 compile fail at link stage when the package apr is installed from sstate cache, so add libtool to SSTATE_SCAN_FILES.
[ CQID: WIND00405372 ]
--- meta/recipes-support/apr/apr_1.4.6.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
meta/recipes-support/apr/apr_1.4.6.bb +2 -2
@@ -9,7 +9,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=0c35ff3c4c83b89d2f076e315caac28b \ BBCLASSEXTEND = "native" -PR = "r1" +PR = "r2" SRC_URI = "${APACHE_MIRROR}/apr/${BPN}-${PV}.tar.bz2 \ file://configure_fixes.patch \
@@ -43,7 +43,7 @@ do_install_append() { cp ${S}/${HOST_SYS}-libtool ${D}${datadir}/build-1/libtool } -SSTATE_SCAN_FILES += "apr_rules.mk" +SSTATE_SCAN_FILES += "apr_rules.mk libtool" SYSROOT_PREPROCESS_FUNCS += "apr_sysroot_preprocess"
Signature · 1 line
1.8.1
Quoted 7 lines · On Sun, Mar 03, 2013 at 08:34:30PM -0500, [email protected] wrote:
From: Jackie Huang <[email protected]>
The hardcoded paths in libtool will cause apache2 compile fail at link stage when the package apr is installed from sstate cache, so add libtool to
SSTATE_SCAN_FILES.[ CQID: WIND00405372 ]
You can drop this.
Quoted 37 lines
Signed-off-by Jackie Huang <[email protected]>Signed-off-by Randy MacLeod <[email protected]>--- meta/recipes-support/apr/apr_1.4.6.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)meta/recipes-support/apr/apr_1.4.6.bb +2
-2@@ -9,7 +9,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=0c35ff3c4c83b89d2f076e315caac28b \ BBCLASSEXTEND = "native" -PR = "r1" +PR = "r2" SRC_URI = "${APACHE_MIRROR}/apr/${BPN}-${PV}.tar.bz2 \ file://configure_fixes.patch \@@ -43,7 +43,7 @@ do_install_append() { cp ${S}/${HOST_SYS}-libtool ${D}${datadir}/build-1/libtool } -SSTATE_SCAN_FILES += "apr_rules.mk" +SSTATE_SCAN_FILES += "apr_rules.mk libtool" SYSROOT_PREPROCESS_FUNCS += "apr_sysroot_preprocess"Signature · 7 lines
1.8.1 _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Quoted 10 lines · Martin Jansa
Quoted 7 lines · On Sun, Mar 03, 2013 at 08:34:30PM -0500, [email protected] wrote:
From: Jackie Huang <[email protected]>
The hardcoded paths in libtool will cause apache2 compile fail at link stage when the package apr is installed from sstate cache, so add libtool to
SSTATE_SCAN_FILES.[ CQID: WIND00405372 ]
You can drop this.
Is this really a big problem? I can understand people wanting to be able to track commits back to defect reports...
Cheers,
Richard
Quoted 8 lines · Richard Purdie
Quoted 7 lines · Martin Jansa
Quoted 6 lines · On Sun, Mar 03, 2013 at 08:34:30PM -0500, [email protected] wrote:
From: Jackie Huang <[email protected]>
The hardcoded paths in libtool will cause apache2 compile fail at link stage when the package apr is installed from sstate cache, so add libtool to
SSTATE_SCAN_FILES.
Quoted 6 lines
Quoted 3 lines
Quoted 1 line
[ CQID: WIND00405372 ]
You can drop this.
Is this really a big problem? I can understand people wanting to be able to track commits back to defect reports...
Not big problem, but isn't link to cgit in their tracking system enough?
That's what I'm using for SHR bugs now, because I cannot assume that people using oe-core will know where bug tracker for [SHR #666] is.
I cannot find public windriver bug tracker where I can search WIND00405372 to find longer description why this change is needed (I know why in this case) - that's why I find yocto bug tags useful, but not WIND00*.
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Quoted 13 lines · Martin Jansa
Quoted 12 lines · Richard Purdie
Quoted 10 lines · Martin Jansa
Quoted 7 lines · On Sun, Mar 03, 2013 at 08:34:30PM -0500, [email protected] wrote:
From: Jackie Huang <[email protected]>
The hardcoded paths in libtool will cause apache2 compile fail at link stage when the package apr is installed from sstate cache, so add libtool to
SSTATE_SCAN_FILES.[ CQID: WIND00405372 ]
You can drop this.
Quoted 7 lines
Quoted 2 lines
Is this really a big problem? I can understand people wanting to be able to track commits back to defect reports...
Not big problem, but isn't link to cgit in their tracking system enough?
That's what I'm using for SHR bugs now, because I cannot assume that people using oe-core will know where bug tracker for [SHR #666] is.
I am quite happy for the meaning of some of these to be documented somewhere with a link to the appropriate bugzillas or other systems.
Quoted 4 lines
I cannot find public windriver bug tracker where I can search WIND00405372 to find longer description why this change is needed (I know why in this case) - that's why I find yocto bug tags useful, but not WIND00*.
As per the commit guidelines, these are additional information and no excuse for not writing a self-standing commit message. Some will be more useful than others but I'm not sure it makes sense to remove them just for the sake of it.
Cheers,
Richard
Quoted 6 lines · Richard Purdie
Quoted 3 lines
Quoted 1 line
[ CQID: WIND00405372 ]
You can drop this.
Is this really a big problem? I can understand people wanting to be able to track commits back to defect reports...
it would not make sense for most of people in community. Having reference to yocto project
bug reports is still some information since people can go and look at the bug.
each one of us have one or another way of internal tracking,
Ah... so CQID is an internal WindRiver thing?
Quoted 1 line · Trevor Woerner
Ah... so CQID is an internal WindRiver thing?
Correct. This is our internal bug tracking number. (Our customers also get access to some of the numbers as well..)
We include this number of items we've ported from our product back to oe-core so that when we uprev it is easier for us to verify that certain problems have been corrected.
If the community decided these numbers are not acceptable we'll stop including them. (If you note, not all of our contributions include those numbers.. generally only bug fixes do.)
--Mark
Quoted 5 lines
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core