<div dir="auto"><div> <div class="gmail_extra"> <div class="gmail_quote">On Feb 20, 2018 12:12 PM, "Aleksander Morgado" <<a href="mailto:aleksander@aleksander.es">aleksander@aleksander.es</a>> wrote: <blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="elided-text">On Tue, Feb 20, 2018 at 7:02 PM, Russ Westrem <<a href="mailto:lspwaterproofing@gmail.com">lspwaterproofing@gmail.com</a>> wrote: > > > On Tue, Feb 20, 2018 at 11:53 AM, Aleksander Morgado > <<a href="mailto:aleksander@aleksander.es">aleksander@aleksander.es</a>> wrote: >> >> Hey! >> >> >> make[8]: Entering directory >> >> >> >> '/home/russ/MM/source/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/libmbim-1.15.0-20161123/src/libmbim-glib' >> >> CC libmbim_glib_core_la-mbim-device.lo >> >> mbim-device.c: In function 'initable_init_async': >> >> mbim-device.c:2168:15: error: assignment from incompatible pointer type >> >> [-Werror=incompatible-pointer-types] >> >> ctx->self = g_object_ref (initable); >> >> ^ >> >> >> > >> > Oh, I think this is a recent change in GLib, which makes >> > g_object_ref() keep the type info in its return value. >> > >> > This specific issue is anyway obsolete in MBIM 1.16.0 as that code was >> > changed during the switch to GTask. I'd suggest you upgrade to 1.16.0 >> > and retry. >> > >> > >> > Still a little new to this. >> > >> > I'm in the libmbim makefile. Where do I find the exact info to put into >> > PKG_VERSION >> > And >> > PKG_SOURCE_VERSION >> > >> > so that I can get the 1.16.0 libmbim >> > >> >> If you want the exact stable version release, you can just refer to >> the tag in PKG_SOURCE_VERSION, e.g. this would probably work: >> >> PKG_VERSION=1.16.0 >> PKG_SOURCE_VERSION=1.16.0 >> >> You could probably just get rid of the second one, but as we're >> building from git you may want in the future to use a newer commit id >> while keeping the PKG_VERSION, or using something like >> 1.16.0-20180220. >> >> If you prefer to refer to the commit id instead: >> >> PKG_VERSION=1.16.0 >> PKG_SOURCE_VERSION=16e15d49297f72397f6b691cf7a9ccf47bdae844 >> >> -- >> Aleksander >> <a href="https://aleksander.es" rel="noreferrer" target="_blank">https://aleksander.es</a> > > > ok did that. Now i have an issue with the patch. > > Applying ./patches/0001-openwrt-remove-docs.patch using plaintext: > patching file Makefile.am > Hunk #1 succeeded at 1 with fuzz 2. > patching file autogen.sh > Hunk #1 FAILED at 14. > 1 out of 1 hunk FAILED -- saving rejects to file autogen.sh.rej > patching file <a href="http://configure.ac" rel="noreferrer" target="_blank">configure.ac</a> > Hunk #1 succeeded at 101 (offset 9 lines). > Hunk #2 succeeded at 157 (offset 8 lines). > Hunk #3 succeeded at 173 (offset 10 lines). > Hunk #4 succeeded at 190 (offset 10 lines). > Patch failed! Please fix ./patches/0001-openwrt-remove-docs.patch! > Makefile:69: recipe for target > '/home/russ/MM/source/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/libmbim-1.16.0/.prepared_961d229cdf252792062ee13983a8daa3_6664517399ebbbc92a37c5bb081b5c53' > failed > </div>What happens if you just remove both patches from the patches/ directory? I should update the openwrt repo with newer versions myself... -- Aleksander <a href="https://aleksander.es" rel="noreferrer" target="_blank">https://aleksander.es</a> </blockquote></div> </div></div><div class="gmail_extra" dir="auto">That worked then had the same issues for libqmi. I updated libqmi to 1.20.0 and then got the patch error. I then removed the libqmi patches as well. </div></div>