On 08/09/2015 07:52 AM, Khem Raj wrote:
On Jul 30, 2015, at 12:40 AM, wenzong fan wenzong@windriver.com wrote:
On 07/29/2015 06:19 PM, Burton, Ross wrote:
On 29 July 2015 at 08:34, wenzong@windriver.com
mailto:wenzong@windriver.com wrote:
+# bjam is already stripped, don't
On Jul 30, 2015, at 12:40 AM, wenzong fan wenzong@windriver.com wrote:
On 07/29/2015 06:19 PM, Burton, Ross wrote:
On 29 July 2015 at 08:34, wenzong@windriver.com
mailto:wenzong@windriver.com wrote:
+# bjam is already stripped, don't strip it again
On 07/29/2015 06:19 PM, Burton, Ross wrote:
On 29 July 2015 at 08:34, wenzong@windriver.com
mailto:wenzong@windriver.com wrote:
+# bjam is already stripped, don't strip it again
+INHIBIT_SYSROOT_STRIP = 1
In case it's even needed to debug bjam-native, how hard would it be to
From: Wenzong Fan wenzong@windriver.com
The bjam is already stripped by default. Fix warning:
WARNING: File '.../tmp/sysroots/x86_64-linux/usr/bin/bjam' from \
bjam-native was already stripped, this will prevent future debugging!
Signed-off-by: Wenzong Fan wenzong@windriver.com
---
On 29 July 2015 at 08:34, wenzong@windriver.com wrote:
+# bjam is already stripped, don't strip it again
+INHIBIT_SYSROOT_STRIP = 1
In case it's even needed to debug bjam-native, how hard would it be to stop
bjam from being stripped in the first place?
Ross
--
