MAybe it's enough to add foreign to Makefile.am
AUTOMAKE_OPTIONS = foreignThen most probably the only think required is to change AC_INIT-AC_INIT +AC_INIT(FULL-PACKAGE-NAME, VERSION, BUG-REPORT-ADDRESS)Reference: http://mij.oltrelinu...oconf-automake/That's already tried by me , but really I never could not let it work. To at to automake in Makefile.am it is
AM_INIT_AUTOMAKE([foreign])
We do never reach the automake stage into bitbake , as it's already failed into autoreconf fase. And that's why the (foreign) patch was made in 2004 into oe-core . It is just removed now and there we go...problems are starting.
Sorry athoik it does well work out.
By the early tests before I did not knew yet that building a package which is using the inherit autotools pkgconfig . Only configures ok when building image.
Which work as example :
MACHINE=vuduo2 bitbake -b /home/christophe/openpli40-master-next/openpli-oe-core/meta-vuplus/recipes-bsp/drivers/gst-plugin-vuplus-dvbmediasink_0.10.bb -f -c cleanall that's ok package fully cleaned.
Which not works after if inherit autotools pkgconfig is used is:
MACHINE=vuduo2 bitbake -b /home/christophe/openpli40-master-next/openpli-oe-core/meta-vuplus/recipes-bsp/drivers/gst-plugin-vuplus-dvbmediasink_0.10.bb Package will fail on configure.
You must use
MACHINE=vuduo2 bitbake openpli-enigma2-feed or You're image to rebuild the package. Then ok.