Skip to contentSkip to conversation

gdb: append to PACKAGECONFIG instead of changing the default

PATCH In review Martin Jansa 1 participant 2 messages Mar 1, 2016

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 gdb: append to PACKAGECONFIG instead of changing the default

* without readline in PACKAGECONFIG and with no-static-libraries.inc gdb fails when trying to build against own bundled static readline

---
 recipes-devtools/gdb/gdb_%.bbappend | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
recipes-devtools/gdb/gdb_%.bbappend +1 -1
index 41592c4..ec17f55 100644
@@ -1 +1 @@
-PACKAGECONFIG ??= "python"
+PACKAGECONFIG_append = " python"
Signature · 1 line
2.7.2
#1 lore raw
Quoted 13 lines · Martin Jansa

* without readline in PACKAGECONFIG and with no-static-libraries.inc gdb fails when trying to build against own bundled static readline

---
 recipes-devtools/gdb/gdb_%.bbappend | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
recipes-devtools/gdb/gdb_%.bbappend +0 -0
index 41592c4..ec17f55 100644

recipes-devtools/gdb/gdb_%.bbappend line 1

Quoted 2 lines
recipes-devtools/gdb/gdb_%.bbappend +1 -1
@@ -1 +1 @@
-PACKAGECONFIG ??= "python"
+PACKAGECONFIG_append = " python"

I should just change this to
PACKAGECONFIG ??= "readline python"

so that it is still easy for DISTROs to override this while fixing gdb build with no-static-libraries.inc until
http://patchwork.openembedded.org/patch/116843/
is merged

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]