Since yesterday building on gentoo works for me now. There would be something totally wrong if compiling sources wouldn’t work on Gentoo
Only thing I needed to do was a
make update-api
as already stated in this thread. And of course I needed to switch back to Python 2.7. make-4.1 didn’t make a problem.
Would be easiest of course. I didn’t check if it’s possible, but I assume it’s intended to be applied in that way, because you need to agree with this license/legal agreements. This proprietary stuff is really a sad thing in the Android world
I took courage from @Arvil’s successful build after another repo sync and started a new compilation (-j8) and got a new error message: make: *** [out/target/product/FP2/obj/GYP/shared_intermediates/blink/platform/ColorData.cpp] Error 127
Did they change code to amend for LED problem and got something wrong? Or has this got nothing to do with the real problem?
Hi! I’d really like to compile as well. As I want to flash this to my FP2, I don’t want to use an unencrypted connection (http) to get the code, so I wanted to register a Gerrit account and use an SSH key as described in the build instructions. I thought that I could directly register for Gerrit … But from this site it seems that I need an account from one of the services mentioned there or have an own website to register at OpenID. (Btw I’m a complete newbie to Gerrit and git (as you now may have already noticed)) However, I neither have a Google, Yahoo or Launchpad account nor do I have a website on my own. Is there another possibility to get a Gerrit account? Or are there providers usable via OpenID other than Google, Yahoo and the others mentioned on the linked page? I hope somone can help me out.
This would be a nice solution as well. Do you suggest to replace “http” by “https” in the following command?
Tested this and works for me. What OS do you have? I think, the package ca-certificates may be missing. (if you are on ubuntu or debian, try installing it with sudo apt-get install ca-certificates)
I’m running Ubuntu 14.04.3 and dpkg -l | grep ca-certificates shows this package to be already installed.
However, nice to know that it works that way for you! That gives me hope to be able to fix this. If someone has another idea, please share it. I’ll also try to do some more research on the error output and the package …
Just create an account with launchpad. That’s the Ubuntu software repository site which also includes bug tracking for ubuntu. It doesn’t hurt to have an account there. You can also use that account for other services like Stackoverflow.
I didn’t want to create a Google account (or a similar one) just for this secondary use case. But you’re right, I can get along with creating a Launchpad account - I see more possible future use cases for this (than for a Google or Yahoo account). Thanks for pointing this out!
I guess for these kind of cases the Docker image is the best bet. There, I’ve figured out all these problems for you and you don’t need to mess around with your system
I don’t think so, but you can always follow the steps described in the How to root with superuser thread afterwards. Since the boot image has been compiled already and can be distributed freely (no blobs in there), this should be pretty straight forward once you have your FP OSOS running on your phone.