Closed yuripourre closed 4 months ago
Could you please share the mozbuild
file you're using?
Could you please share the
mozbuild
file you're using?
Also did mach bootstrap
went well with no issues?
Could you please share the
mozbuild
file you're using?
Thanks for the reply! Sure, I can share but I haven't touched it. It would be the same as the one in the gecko-dev repo.
Also did
mach bootstrap
went well with no issues?
No, actually the error happens exactly when I run ./mach bootstrap
.
Could you please share the
mozbuild
file you're using?Thanks for the reply! Sure, I can share but I haven't touched it. It would be the same as the one in the gecko-dev repo.
Also did
mach bootstrap
went well with no issues?No, actually the error happens exactly when I run
./mach bootstrap
.
Right, again the problem of bootstrap ever changing the dependencies it downloads depending on the date you execute it :(. I am not sure there is an easy fix for that. I don't want to change my dev environment now that we're in the middle of a release but I can try to reproduce the issue after that
@svillar Thank you, I appreciate your efforts. I will try some ideas this weekend and I will update here if I have some progress.
The following methods can be used to build Download gecko124.0.1 and then build the environment in gecko124.0.1
./mach bootstrap
Switch to gecko121.0.1 again to build
./mach build
Thank you @weller0! That worked! I could proceed after using your suggestion.
I had more errors, fixed some and currently struggling with libclang_rt.builtins-aarch64-android.a
not found. I am trying to compile the compiler-rt but having issues in Fedora, apparently some internal packages cannot be found (Fedora problems, no worries).
I think we consider it closed now. Thank you very much!
can refer to : https://bugzilla.mozilla.org/show_bug.cgi?id=1906930
Configuration
Wolvic version: master Wolvic build ID: -
Hardware: Dell Inspiron 15 7000 / Fedora 38
Steps to Reproduce
./mach bootstrap
Current Behavior
Build fails with the following error:
Expected Behavior
Command would succeed
Possible Solution
Context
Error Logs and Stack Traces