binconfig-disabled: write an message to stderr to help confused developers

Often configure scripts or Makefiles that use the stub scripts written by
binconfig-disabled fail mysteriously with no obvious problem.  Attempt to solve
this by writing an error to stderr which hopefully makes it to the logs.

[ YOCTO #8169 ]

(From OE-Core rev: c38acd720b3f6ffbeb544063692eb471dada8593)

Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 2 insertions, 1 deletions

diff --git a/meta/classes/binconfig-disabled.bbclass b/meta/classes/binconfig-disabled.bbclass
index 595cd096f5..602a669aa1 100644
--- a/meta/classes/binconfig-disabled.bbclass
+++ b/meta/classes/binconfig-disabled.bbclass
@@ -9,9 +9,10 @@ FILES_${PN}-dev += "${bindir}/*-config"
 
 do_install_append () {
         for x in ${BINCONFIG}; do
-                echo "#!/bin/sh" > ${D}$x
                 # Make the disabled script emit invalid parameters for those configure
                 # scripts which call it without checking the return code.
+                echo "#!/bin/sh" > ${D}$x
+                echo "echo 'ERROR: $x should not be used, use an alternative such as pkg-config' >&2" >> ${D}$x
                 echo "echo '--should-not-have-used-$x'" >> ${D}$x
                 echo "exit 1" >> ${D}$x
         done