On Tue, Feb 18, 2020 at 6:37 PM Untitled X <[email protected]> wrote:
>
> Hey thanks again Robert for going out of your way to provide a procedure for 
> 3.14.x , and especially for replying while away on your holiday!
>
> Following the procedure for the dpkg method, in which the file 
> "0001-mmc-Allow-forwar-compatibility-for-eMMC.patch" in placed in 
> /yakbuild/patches/local_patches/ and then running ."/build_sh"  seems to work 
> ok on my Ubuntu 19.10 VM,  it yielded me the following files in the 
> /yakbuild/deploy/
>
> linux-firmware-image-3.14.77-ti-r90_1xross_armfhf.deb
> linux-headers-3.14.77-ti-r90_1xross_armhf.deb
> linux-image-3.14.77-ti-r90_1xross_armhf.deb
> linux-libc-dev_1xross_armhf.deb
>
> Placing the file "linux-image-3.14.77-ti-r90_1xross_armhf.deb" on my BBB 
> attempting to run the command "sudo dpkg -i 
> linux-image-3.14.77-ti-r90_1xross_armhf.deb" however gave me the following 
> error:
>
> dpkg-deb error: archive 'linux-image-3.14.77-ti-r90_1xross_armhf.deb" 
> contains not understood data member control.tar.xz, giving up
> dpkg: error processing linux-image-3.14.77-ti-r90_1xross_armhf.deb 
> (--install):
>  subprocess dpkg-deb --control returned error exit status 2
> Errors were encountered while processing:
>  linux-image-3.14.77-ti-r90_1xross_armhf.deb

Ah crap, so we had a workaround for "3.8.13" to detect this, but it
got ignored on "3.14.x"... This should fix it:

https://github.com/RobertCNelson/yakbuild/commit/991c2f18f94d490861776a92424fba2d560660b1

Just run:

git pull ; ./build_deb.sh

and it "should" work this time.. fingers crossed..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYhpx_oYOaeop_xDEjUaHiU0vd1xfca44Lcn53YdHLzmYg%40mail.gmail.com.

Reply via email to