BtbN / FFmpeg-Builds

MIT License
6.97k stars 956 forks source link

could not read /data/FFmpeg-Builds/.cache/images/base/index.json #364

Closed sunpengfei0307 closed 2 months ago

sunpengfei0307 commented 2 months ago

Hi! boy, I have a compile problem just like the title, need some help! Thank you! Linux ubuntu 5.15.0-102-generic #112-Ubuntu SMP Tue Mar 5 16:50:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux (vmware) image

BtbN commented 2 months ago

Just ignore that, there simply is no cache on first build.

sunpengfei0307 commented 2 months ago

Thank you! but I can't build success and get ffmpeg bin. 1、./build.sh linux64 nonfree 6.0 lto, errors like this and abort!

2、./makeimage.sh linux64 nonfree 6.0 lto, errors like this and abort! ERROR: could not read /data/FFmpeg-Builds/.cache/images/base/index.json: open /data/FFmpeg-Builds/.cache/images/base/index.json: no such file or directory

BtbN commented 2 months ago

The first error is because the second step did not complete. And the second one simply is not an error. Both of these outputs are expected and normal. So there has to be an actual error further up somewhere.

Also, you don't need a nonfree build for any of the stuff you listed. The only difference in a nonfree build is that libfdkaac is present.

sunpengfei0307 commented 2 months ago

The first error is because the second step did not complete. And the second one simply is not an error. Both of these outputs are expected and normal. So there has to be an actual error further up somewhere.

Also, you don't need a nonfree build for any of the stuff you listed. The only difference in a nonfree build is that libfdkaac is present.

Yes, if the first error (not find) is not resolved, the compilation script will exit directly from my end, and I will not be able to proceed with the subsequent steps. I am not sure what to do now. I really hope some assistance in resolving this error or bypassing it! best wishs to you!

BtbN commented 2 months ago

Again, it not finding the cache is not an error. It printing that is normal and expected. Please find the actual error in your logs, otherwise there is nothing I can do for you.