I had cm7 on it when I ran the extract, I just did it on that phone bricker build as well, only ended up missing one *.so, cant remember which exact file it was, had to step away. Will get back in the am.

Sent from my SGH-I777 using XDA

Update: Just flashed atinm's nightly of CM9, ran extract_files.sh and no errors at all.

Originally Posted by 5942marine

I tried to run extract-files.sh and got:

remote object '/system/lib/libGLESv2_dbg.so' does not exist

Which gave me this during compile:

make: *** No rule to make target `vendor/samsung/galaxys2-common/proprietary/libGLESv2_dbg.so', needed by `out/target/product/i777/system/lib/libGLESv2_dbg.so'.  Stop.

I have the latest repo as describe in the op. Anyone else run into this issue? Ran the extract on cm7.

Originally Posted by 5942marine

I had cm7 on it when I ran the extract, I just did it on that phone bricker build as well, only ended up missing one *.so, cant remember which exact file it was, had to step away. Will get back in the am.

Sent from my SGH-I777 using XDA

Update: Just flashed atinm's nightly of CM9, ran extract_files.sh and no errors at all.

Confirmed, /system/lib/libGLESv2_dbg.so does not exist in CM7 so of course it can't be extracted. Screencap of partial file list from my last nandroid on CM7 before upgrading attached.

All non-dev related posts have been moved over to the General CM9 thread.

I guess the giant red bolded DEV tag at the top isnt obvious enough.

Just an update... I was compiling the latest build, and got the following error:

make: *** No rule to make target `vendor/samsung/galaxys2-common/proprietary/hwcomposer/lib/libfimc.so', needed by `out/target/product/i777/obj/lib/libfimc.so'.  Stop.

Now, when i ran ./extract-files, I didn't recieve any errors while it was pulling the files.

I can see that the file is in the galaxy2-common directory, under the proprietary folder.

There is not folder under proprietary /hwcomposer/lib

Originally Posted by 5942marine

Just an update... I was compiling the latest build, and got the following error:

make: *** No rule to make target `vendor/samsung/galaxys2-common/proprietary/hwcomposer/lib/libfimc.so', needed by `out/target/product/i777/obj/lib/libfimc.so'.  Stop.

Now, when i ran ./extract-files, I didn't recieve any errors while it was pulling the files.

I can see that the file is in the galaxy2-common directory, under the proprietary folder.

There is not folder under proprietary /hwcomposer/lib

This is the fix for the same issue that was present in galaxys2:
http://review.cyanogenmod.com/#change,13935

Posts cleaned out again. Im only going to say this one last time...
THIS THREAD IS FOR DEVELOPMENT ONLY. IF YOU ARE NOT HELPING DEVELOP FOR CM9 THEN YOU SHOULD POST IN THE GENERAL THREAD, NOT THIS THREAD. ANY FURTHER NON-DEV RELATED POSTS WILL RECEIVE AN AUTOMATIC INFRACTION AND THEIR POST WILL BE DELETED.

Originally Posted by sam3000

This is the fix for the same issue that was present in galaxys2:
http://review.cyanogenmod.com/#change,13935

Thanks, got it working.

Originally Posted by sam3000

This is the fix for the same issue that was present in galaxys2:
http://review.cyanogenmod.com/#change,13935

http://review.cyanogenmod.com/#change,14155 fixes the same thing for i777.

Originally Posted by 5942marine

Thanks, got it working.

Any extract-files.sh fixes you make - please gerrit them, or just send them to me directly via email if you don't know gerrit (learn Gerrit if you intend to develop for CM!).

Originally Posted by Red5

All non-dev related posts have been moved over to the General CM9 thread.

I guess the giant red bolded DEV tag at the top isnt obvious enough.

Can you clarify - I take it discussion about build issues that are because script fixups are necessary in github sources is also off-limits ? ie where the root issue is in the repo not the person trying to compile. (Previous post removal implies this.)

If someone can't massage whatever comes out of github in order to get it to compile then it's unlikely they would be posting patches even if the build worked. However, on the other hand, I would argue it's also useful to identify, discuss and fix any build related issues for the benefit of all (separate thread perhaps?)