[Q] [Rom Building] How to deal with this error topic

heyyo, build question here.

1. i hope i dont bother someone, because this is carbon building and not in their threat, but i'm not sure if this error is really related to there git?

2. OS info: i'm currently running on antergos, an arch based linux distro, therefor i'm using the arch wiki for setting up the building enviroment, more here:
https://wiki.archlinux.org/index.php...ilding_Android

3. the lower part is taken from the official carbon githubt, more here:
https://github.com/CarbonDev/android


the terminal input


mkdir ~/bin
export PATH=~/bin:$PATH
curl http://commondatastorage.googleapis....downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo

mkdir carbon
cd carbon

virtualenv2 venv # Creates a directory, venv/, containing the Virtualenv
source venv/bin/activate

repo init -u https://github.com/CarbonDev/android.git -b kk && repo sync -f

. build/envsetup.sh

lunch 23
make carbon -j5


then i get this error output (after about 1:20h):

Gyp action: third_party_WebKit_Source_core_core_derived_source s_gyp_make_derived_sources_target_CSSValueKeywords (/home/nik/carbon/out/target/product/exhilarate/obj/GYP/shared_intermediates/blink/CSSValueKeywords.cpp)
Traceback (most recent call last):
File "scripts/make_css_property_names.py", line 238, in <module>
in_generator.Maker(CSSPropertiesWriter).main(sys.a rgv)
File "/home/nik/carbon/external/chromium_org/third_party/WebKit/Source/core/scripts/in_generator.py", line 119, in main
writer.write_files(options.output_dir)
File "/home/nik/carbon/external/chromium_org/third_party/WebKit/Source/core/scripts/in_generator.py", line 77, in write_files
self._write_file(output_dir, generator(), file_name)
File "scripts/make_css_property_names.py", line 233, in generate_implementation
gperf = subprocess.Popen(gperf_args, stdin=subprocess.PIPE, stdout=subprocess.PIPE)
File "/usr/lib64/python2.7/subprocess.py", line 709, in __init__
errread, errwrite)
File "/usr/lib64/python2.7/subprocess.py", line 1326, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
external/chromium_org/third_party/WebKit/Source/core/make_derived_sources.target.linux-arm.mk:74: recipe for target '/home/nik/carbon/out/target/product/exhilarate/obj/GYP/shared_intermediates/blink/CSSPropertyNames.cpp' failed
make: *** [/home/nik/carbon/out/target/product/exhilarate/obj/GYP/shared_intermediates/blink/CSSPropertyNames.cpp] Error 1
make: *** Waiting for unfinished jobs....
Traceback (most recent call last):
File "scripts/make_css_value_keywords.py", line 177, in <module>
in_generator.Maker(CSSValueKeywordsWriter).main(sy s.argv)
File "/home/nik/carbon/external/chromium_org/third_party/WebKit/Source/core/scripts/in_generator.py", line 119, in main
writer.write_files(options.output_dir)
File "/home/nik/carbon/external/chromium_org/third_party/WebKit/Source/core/scripts/in_generator.py", line 77, in write_files
self._write_file(output_dir, generator(), file_name)
File "scripts/make_css_value_keywords.py", line 172, in generate_implementation
gperf = subprocess.Popen(gperf_args, stdin=subprocess.PIPE, stdout=subprocess.PIPE)
File "/usr/lib64/python2.7/subprocess.py", line 709, in __init__
errread, errwrite)
File "/usr/lib64/python2.7/subprocess.py", line 1326, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
external/chromium_org/third_party/WebKit/Source/core/make_derived_sources.target.linux-arm.mk:108: recipe for target '/home/nik/carbon/out/target/product/exhilarate/obj/GYP/shared_intermediates/blink/CSSValueKeywords.cpp' failed
make: *** [/home/nik/carbon/out/target/product/exhilarate/obj/GYP/shared_intermediates/blink/CSSValueKeywords.cpp] Error 1


any idea? Thanks in advance ;)

Lenovo nears $3 billion deal to buy Google's Motorola unit topic

Hrm. I guess no more Nexuses (Nexii?) or Moto Xs? We need someone to champion the pure Android experience with timely updates (a la Apple and iOS)!

More on the sadness at http://www.reuters.com/article/2014/...A0S1YN20140129...

[FAQ} Root Mini-FAQ: What's the big deal with root? topic

This topic deals specifically with root accessbility. For other topics, please consult the Chromecast FAQ thread or Search.

Are all Chromecasts rootable?
NO! Only those shipped with the original vulnerable bootloader can be rooted. See the Rootable Serial Numbers thread for guidance.


Root now or root later? Why do I need to root before setting up and using the device?
THERE IS NO OPTION TO ROOT LATER!
Short of finding a new root method, the bootloader is the only way to write to the device and therefore change the filesystem, which is what is necessary for injecting root.
Google's OTA update will update the bootloader and patch the vulnerability FlashCast uses to be able to write to the device and get root and disable Google OTAs (so the hole does not get patched).


Do I even need root?
Initially there were more reasons to root, like the ability to send local files to Chromecast. However, new Google-approved apps like Avia, RealPlayer Cloud and Plex were released to bridge that gap.
So right now, functionality-wise, root brings you Eureka-ROM.
Eureka-ROM brings you...

• Custom whitelist (run apps not whitelisted/approved by Google)


• DHCP client control (use static address)


• DNS control (use non-Google DNS)


• Status (temperature reporting, IP, firmware)


• ADB on/off


• Telnet on/off


• SSH on/off

Likely more will come in the future.
DNS control is important for people using Chromecast outside of the US, as many of the Chromecast services like Netflix and Hulu Plus are either unavailable or have restrictions on available content in other countries.


Why can't we get root another way?
While I'm not one to say never, because there are a lot of clever people out there but...
Unlike phones and tablets, Chromecast is quite the ornery Android device...

1. It has no Fastboot.
   So we can't download a new ROM image that way.


2. It has no accessible recovery.
   So we can't install stuff of access the filesystem with an update.zip


3. It has no image loader/flasher utility.
   So we can't download a new ROM image that way either.


4. It has no interface (screen or input device).
   This just makes it even more difficult to interact with it for hacking purposes.


5. ADB, Telnet and SSH are disabled by default.
   No ways to peek or poke around there either.


6. The runtime filesystem is read-only.
   So a clever app can't make changes either.


7. Google OTA updates are automatically downloaded and applied, updating the bootloader and ROM. Updated bootloader versions will only execute Google-signed code.
   So once you get a Google OTA update, you lose the ability to update the ROM (without a new root method).

Long story short, to get root you need to access the filesystem or execute custom (not signed by Google) code.
But you can't access the filesystem.
And you can only execute custom code on the original bootloader (build 12072).
Perhaps, once the SDK is released, we could see some kind of permissions exploit that could allow a clever app to somehow obtain root access to update the system or write a vulnerable bootloader, but that remains to be seen.


Well that pisses me off! Google is evil! I deserve root!! I'm buying something else!!!
Google never promised root. They just promised an SDK, which is still in development. Root capability just came as an unexpected (and perhaps unintended) gift for initial units.
Chromecast is not a phone or tablet. It's a appliance to be connected to a TV. Hacking your TV might be fun, but Chromecast is not aimed at hackers. It's aimed at the normal people who just want to get Netflix, YouTube, etc on their TV and people who like the concept of using the Android or iOS device instead of adding yet another remote control to their pile.
Whether you buy Chromecast is your choice. Nobody said you had to buy every new device Google puts out. Google isn't Apple.
Also keep in mind, Chromecast is useless without content, which requires content providers. Content providers don't like the concept of root access to a device that plays their content. They fear it will allow their content to easily be pirated. That's why CinemaNow and other services don't allow rooted devices.
For the longevity of the device and continued usability for normal customers, it's in Google's best interest not to have widespread/publicized hacking of Chromecast. Long story short, even with thousands of rooted Chromecasts, we're still a minority compared to the millions of Chromecasts out in the market.