The tool "populatefs" does refuse to open part2.ext4
The file is there and I was able to mount it to some folder. I think the problem might be in populatefs.
File permissions are ok?
Posts by vpeter
-
-
CodeError: [Filesystem error] /tmp/tmp.7W2JyYfMyC/part2.ext4 cannot be opened.
This same error was reported not long back. No idea why it happens. That's why you will need to debug it yourself - put some echo's and ls in scripts/mkimage to see why it happens. -
There is a known problem with this particular version of gcc.
Which problem exactly?We don't have any build issue with 7.0.2.
-
Sorry I don't understand
Same here
-
Sorry TVPL but I don't know what kind of display is this.
But because RPi is using sd card for libreelec it very easy to test
-
7.90.003 doesn't include any extra imx6 patch. Because of that some functionality seems better (like in your case) but other were worst.
7.90.005 includes only small changes to upstream kodi (to even compile it for imx6). Nothing else. If you have an issue with this version it is a problem with some upstream commits mk01 did. But because no one has any contact with him there is not much hope for a fix. -
Try
Codekodi-send -a "PlayMedia(/path/to/movie.mkv)" -
What is a the correct phrase?
I think XN,C to Kodi. But I don't see error in transifex? -
7.90.004 image build. This one is still using huge patch based on xbian's kodi which includes more changes to kodi. In 005 I didn't do that anymore because it is hard to get this working. Maybe I should look this again... That's why images from 005 on are using only original kodi + some small patches.
-
escalade, you are correct: enabling autoreconf should fix this issue because I don't see warning anymore with my patch. Seems this should be done for some other packages too (I noticed warnings with libressl, glib, libX11, libdrm, alsa-lib, and few others).
And yes, this patch will be PR-ed. First I need to build all projects to confirm they at least build. -
I suspect this problem happen because of -rpath /usr/lib in command line when linking. Rpath is used to add folder for runtime linker but also when locating shared objects included in the link. I assume in this case libressl is installed on your host and it is picked because of this. But usually such incompatible binaries are just skipped. Not sure why this didn't happen in this case.
Yorker, put this patch file to folder packages/devel/binutils/patches. Remove whole build folder and build whole image again. I think it should fix your issue.
Please report back if it works or not.
-
Are you saying that with diskpart you can't destroy system disk? Good to know that
-
No really suggestions.
This happens on every build? -
The risk with diskpart is that you select the wrong disk (in the case where you have multiple disks). Then of course you will wipe the wrong disk.The same risk exists with your solution. If you write image to wrong disk...then you wipe the wrong disk. Same risk.
Not true: usb creator app writes only to removable drives and you can't overwrite system disk. -
Which LE version was last fine? This problem happen only with livestream?
There has been lot of changes regarding kodi. Previously I used big patch from xbian. But because it was to hard to separate it from theirs kodi repo I switched to patches from openbricks. Also mk01 did lot of work in upstream kodi. And everything is just a big mess at the end.
Obviously I can't fix such errors.
-
Yes, be very, very careful with using diskpart - easy to trash the disk. Safer solution was proposed by me.
-
Linux stat commands show: IO Block: 1024
And I don't think we have somethnig different for Virtual builds.A little more technical view of data captured with Wireshark:
samba.conf allocation roundup size = 0
Allocation size: 1024
iW30Oz.jpgsamba.conf allocation roundup size = 4096
Allocation size: 4096
nKVYiG.jpg -
Using LibreELEC (community) Version: 7.90.009 - Virtual.x86_64-7.90.009:
Codesamba.conf allocation roundup size = 0 Size on disk Windows 7: 1.00 KB (1.024 bytes) Windows 10: 1.00 KB (1,024 bytes) samba.conf allocation roundup size = 4096 Size on disk Windows 7: 1.00 KB (1.024 bytes) Windows 10: 4.00 KB (4,096 bytes)