yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] rodman01:
Only delete or comment out the mentioned lines from the config.xml in your device overlay folder.....path and line numbers are in your error message.
[Android Q&A, Help & Troubleshooting] Quasar:
I suspect you're using the CM device tree directly. I suppose you'll have to adapt the CM tree to beanstalk. Then it'll work.
[Android Q&A, Help & Troubleshooting] armkreuz:
Ok nice, I found:

Had to change device/samsung/jfltetmo/cm.mk

vendor/cm/config to vendor/beanstalk/config and cm_jftetmo to bs_jfletmo
[Android Q&A, Help & Troubleshooting] adinkwok:
You can delete cm.mk, you don't need it for compiling other Roms.
[Android Q&A, Help & Troubleshooting] domenicogalati45:
Hi guys , can you help me to find from where this error come from? http://pastebin.com/6k1CMXcN please, it is very important.

Inviato dal mio ME173X utilizzando Tapatalk
[Android Q&A, Help & Troubleshooting] epicboy:
Hey everyone. So I just finished building OmniROM 5.0 for my device. Towards the end of the terminal output, It said

The device will not boot past the kernel splash screen. Does anyone know how to reduce the size of the boot partition or know how to repartition a device?

My device is the Samsung T959 Vibrant which is MTD compatible.
[Android Q&A, Help & Troubleshooting] adinkwok:
You can change the sizes of partitions within your device tree (I think it's in the Boardconfig)
[Android Q&A, Help & Troubleshooting] epicboy:
Sorry if I'm a bother but can you please look at my device tree and help me out more? I'm not good with source code [emoji16]
[Android Q&A, Help & Troubleshooting] MasterAwesome:
It's not the size of the boot partition! It's 83% so it's good to go. The thing is there's an error while loading the kernel, go back to your stock rom/ working rom. Create your kernel and use it as an alternative boot image and flash it using dd or fastboot to check if this problem is with the kernel or with the os. If the os is the problem your board configuration most have been wrongly setup for your device. Good luck

Regards.
[Android Q&A, Help & Troubleshooting] StrangerWeather:
Hi guys, getting these errors:

I would add the resources but I don't understand what is meant by "base package". Where is it? Also, is there a particular format I need to use to add the resources or is it just <add-resource> followed by config_wifiApFirmwareReload etc. ?

Cheers!:)
[Android Q&A, Help & Troubleshooting] MasterAwesome:
The base package is the framework/base. The source is there. There's also a config.xml there to specify all the tags you can override from the device tree. Good luck
[Android Q&A, Help & Troubleshooting] ##W4TCH0UT##:
Just comment out those lines causing errors..
[Android Q&A, Help & Troubleshooting] MasterAwesome:
-Ignore -
[Android Q&A, Help & Troubleshooting] Gokulbalram:
Hey guys, I'm building for a ROM called 'OwnROM' (i9300) and this is what I get:

build/core/tasks/kernel.mk:91: **********************************************************
build/core/tasks/kernel.mk:92: * Kernel source found, but no configuration was defined *
build/core/tasks/kernel.mk:93: * Please add the TARGET_KERNEL_CONFIG variable to your *
build/core/tasks/kernel.mk:94: * BoardConfig.mk file *
build/core/tasks/kernel.mk:95: **********************************************************
make: *** No rule to make target `ownrom'. Stop.

I checked and there is a configuration for TARGET_KERNEL_CONFIG (cyanogenmod_i9300_defconfig), yet it doesn't build. Can somebody help?
[Android Q&A, Help & Troubleshooting] adinkwok:
Did you check that there is a defconfig is named cyanogenmod_i9300_defconfig? Maybe the depencies synced the wrong kernel source? (Its happened to me before)
[Android Q&A, Help & Troubleshooting] Tomoms:
Hi guys, I have a question. I'm trying to build Cyanogenmod 12 for a supported device. After initializing "repo" with

repo init -u GIT_URL -b cm-12.0

I know I have to sync the repos with

repo sync

Why do I have to download 10 GB or more of code when the resulting zip will be around 250MB? I mean: when syncing the repos, the terminal output displays various messages, numbers, file sizes, network speed etc., but it also shows that it's downloading the code of all the previous versions of android: something like 4.0.0_r1, 4.1.2, 4.4_r1 and 5.0.1_r1.

Is there a way of downloading only Lollipop's code instead of several GB's of useless code?

Thanks
[Android Q&A, Help & Troubleshooting] adinkwok:
It doesn't download all those branches, its just showing that those repos have other branches in them (so that the developers of the ROM can pull and merge from them if needed). Android source is naturally that big; it is full of many files that create specific modules and such based on the device tree.
[Android Q&A, Help & Troubleshooting] Tomoms:
Thanks, so it is normal that we need 10 GB of code to create a 250 MB zip. Thank you for pointing this out to me, as searching on google I understood wrong things.
[Android Q&A, Help & Troubleshooting] hell_lock:
I'm encountering this error while building cm11 on my machine.

In file included from hardware/qcom/display-caf-new/liboverlay/overlayRotator.h:35:0,
from hardware/qcom/display-caf-new/libhwcomposer/hwc_utils.h:34,
from hardware/qcom/display-caf-new/libqdutils/cb_utils.h:33,
from hardware/qcom/display-caf-new/libqdutils/cb_utils.cpp:28:
hardware/qcom/display-caf-new/liboverlay/mdpWrapper.h:72:36: error: 'mdp_overlay_list' has not been declared
In file included from hardware/qcom/display-caf-new/liboverlay/overlayRotator.h:35:0,
from hardware/qcom/display-caf-new/libhwcomposer/hwc_utils.h:34,
from hardware/qcom/display-caf-new/libqdutils/cb_utils.h:33,
from hardware/qcom/display-caf-new/libqdutils/cb_utils.cpp:28:
hardware/qcom/display-caf-new/liboverlay/mdpWrapper.h:180:43: error: 'mdp_overlay_list' has not been declared
hardware/qcom/display-caf-new/liboverlay/mdpWrapper.h: In function 'bool overlay::mdp_wrapper::validateAndSet(const int&, int&)':
hardware/qcom/display-caf-new/liboverlay/mdpWrapper.h:182:19: error: 'MSMFB_OVERLAY_PREPARE' was not declared in this scope
build/core/binary.mk:432: recipe for target '/home/prototype-u/cm11/out/target/product/flamingo/obj/SHAR

Device tree: https://github.com/CyanogenMod/android_device_sony_flamingo

Kernel: https://github.com/prototype-U/SXE3-Kernel

I hope anyone can help me on this..

Thanks and regards.
[Android Q&A, Help & Troubleshooting] MasterAwesome:
What I can see in this output here is that the problem is not with the kernel nor with the device source. And looks like it's an error with the toolchain you're using. Cause it builds fine for me. Try using gcc-4.7.
[Android Q&A, Help & Troubleshooting] Gokulbalram:
The device tree and the source are from CM. I found cyanogenmod_i9300_defconfig in /kernel/samsung/i9300/arch/arm/configs. I can't figure what's wrong here.
[Android Q&A, Help & Troubleshooting] MasterAwesome:
Post your kernel related tags in the boardconfig.mk here.
[Android Q&A, Help & Troubleshooting] Gokulbalram:
The BoardConfig.mk:

#
# Copyright (C) 2012 The CyanogenMod Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#

# This variable is set first, so it can be overridden
# by BoardConfigVendor.mk

-include device/samsung/smdk4412-common/BoardCommonConfig.mk

# RIL
BOARD_PROVIDES_LIBRIL := true
BOARD_MODEM_TYPE := xmm6262
BOARD_RIL_CLASS := ../../../hardware/samsung/ril

# Bluetooth
BOARD_BLUETOOTH_BDROID_BUILDCFG_INCLUDE_DIR := device/samsung/i9300/bluetooth

[B]# Kernel
TARGET_KERNEL_SOURCE := kernel/samsung/smdk4412
TARGET_KERNEL_CONFIG := cyanogenmod_i9300_defconfig[/B]

# Recovery
TARGET_RECOVERY_FSTAB := device/samsung/i9300/rootdir/fstab.smdk4x12
RECOVERY_FSTAB_VERSION := 2

# Selinux
#BOARD_SEPOLICY_DIRS += \
# device/samsung/i9300/selinux

#BOARD_SEPOLICY_UNION += \
# device.te \
# domain.te \
# file.te \
# file_contexts \
# init.te \
# mediaserver.te \
# rild.te \
# system.te \
# ueventd.te \
# wpa_supplicant.te

# assert
TARGET_OTA_ASSERT_DEVICE := m0,i9300,GT-I9300

# own headers
TARGET_SPECIFIC_HEADER_PATH := device/samsung/i9300/include

# inherit from the proprietary version
-include vendor/samsung/i9300/BoardConfigVendor.mk

and the cyanogenmod_i9300_defconfig:

[IMG="Lol"]http://i.imgur.com/rkC2q9o.png[/IMG]

EDIT: ROM source (ROM was supposed to use ArchiDroid kernel and tree, but I download CM's source and tree manually): https://github.com/OwnROM

Kernel: https://github.com/CyanogenMod/android_kernel_samsung_smdk4412

Tree: https://github.com/CyanogenMod/android_device_samsung_i9300

Common tree: https://github.com/CyanogenMod/android_device_samsung_smdk4412-common
[Android Q&A, Help & Troubleshooting] StrangerWeather:
Many thanks for your replies to my previous question.

If you could have a look at this, I would be grateful. I am trying to build Omnirom 5.0 for falcon.

http://pastebin.com/1e34Pqwk

Thanks for any help! :)
[Android Q&A, Help & Troubleshooting] MasterAwesome:
I've found the error, in the previous post, your path to your kernel is kernel/samsung/i9300 but here it's defined as kernel/samsung/smdk4412 so the path is wrong. Fix it and you should be good to go. Good luck

Regards

---------- Post added at 05:58 PM ---------- Previous post was at 05:49 PM ----------

It's pretty straightforward, it says the value it's getting from the stuct is == some predefined value ' VDEC_CODECTYPE_MVC' but it's not available for if function to check if they are equal. As I said before,your tool chain is bad or your source is bad, try pulling cyanogenmod source for that particular git and merging it. If that doesn't help then definitely your tool chain.
[Android Q&A, Help & Troubleshooting] Gokulbalram:
Are you sure? Because kernel is supposed to be smdk4412. I shall try and report in some time though.
[Android Q&A, Help & Troubleshooting] MasterAwesome:
Just do a "make bootimage" to check if it works.
[Android Q&A, Help & Troubleshooting] Gokulbalram:
I tried the previous suggestion and that didn't work. However, after running 'make bootimage', I get this:

arch/arm/mach-exynos/Kconfig:875:warning: choice value used outside its choice group
arch/arm/mach-exynos/Kconfig:877:warning: defaults for choice values not supported
***
*** Configuration file ".config" not found!
***
*** Please run some configurator (e.g. "make oldconfig" or
*** "make menuconfig" or "make xconfig").
***
make[2]: *** [silentoldconfig] Error 1
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target `bootimage'. Stop.

#### make failed to build some targets (14 seconds) ####

I'll try deleting Roomservice and trees and stuff and redoing it.
[Android Q&A, Help & Troubleshooting] MasterAwesome:
Just go to your kernel source and manually try make insertdefonfignamehere, then type make zImage. I think the values in your configuration file is wrong. Check this before deleting the source.

Remember to export path, cross_compile and arch tags.
[Android Q&A, Help & Troubleshooting] Gokulbalram:
I tried 'make cyanogenmod_i9300_defconfig' and now, I get this:

alectradar@Inspiron-1464:/media/alectradar/sdb3/OwnROM/Lollipop/kernel/samsung/smdk4412$ make bootimage
make: /opt/toolchains/arm-2010q1/bin/arm-none-linux-gnueabi-gcc: Command not found
make: *** No rule to make target `bootimage'. Stop.

#### make failed to build some targets ####

Not really sure on what the last sentence means

EDIT: Didn't see 'make zImage. I just ran it and I get this:

alectradar@Inspiron-1464:/media/alectradar/sdb3/OwnROM/Lollipop/kernel/samsung/smdk4412$ make zImage
make: /opt/toolchains/arm-2010q1/bin/arm-none-linux-gnueabi-gcc: Command not found
CHK include/linux/version.h
UPD include/linux/version.h
CHK include/generated/utsrelease.h
UPD include/generated/utsrelease.h
Generating include/generated/mach-types.h
CC kernel/bounds.s
/bin/sh: 1: /opt/toolchains/arm-2010q1/bin/arm-none-linux-gnueabi-gcc: not found
make[1]: *** [kernel/bounds.s] Error 127
make: *** [prepare0] Error 2

#### make failed to build some targets (15 seconds) ####
[Android Q&A, Help & Troubleshooting] MasterAwesome:
As I said in my previous post you havent exported the path for the toolchain/compiler. Execute this:

export PATH="/media/alectradar/sdb3/OwnROM/Lollipop/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6":$PATH&&export CROSS_COMPILE=arm-eabi- && export ARCH=arm

Looks like you are trying to compile from an external hardrive or a partition of an internal hardrive?
[Android Q&A, Help & Troubleshooting] Gokulbalram:
I tried that and now this:

make: /opt/toolchains/arm-2010q1/bin/arm-none-linux-gnueabi-gcc: Command not found
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CC kernel/bounds.s
/bin/sh: 1: /opt/toolchains/arm-2010q1/bin/arm-none-linux-gnueabi-gcc: not found
make[1]: *** [kernel/bounds.s] Error 127
make: *** [prepare0] Error 2

Yes, It's an external NTFS drive which I mounted as executable.
[Android Q&A, Help & Troubleshooting] MasterAwesome:
I would prefer an ext4 partition, nevertheless the path I gave was wrong you missed a subfolder there. It should navigate to the bin folder of the tool chain. Go to the tool chain folder and go to the bin folder and then copy path and export it.
[Android Q&A, Help & Troubleshooting] Gokulbalram:
I'm not so sure on how to do that :confused:
[Android Q&A, Help & Troubleshooting] MasterAwesome:
Go to the tool chain folder and send me a screen shot
[Android Q&A, Help & Troubleshooting] Gokulbalram:
I'm not really.. sure where that is (sorry)
[Android Q&A, Help & Troubleshooting] MasterAwesome:
Well, a tool chain is basically a compiler used to compile a c program on a particular type of cpu architecture. Suppose you were to make a c program to print hello world. To run on Linux you'd compile it using native tool chain (compilers) but to use the program in Android you would have to 'cross-compile'. The pre-built binary of the compiler is available in the source code. Usually in the prebuilts folder. Navigate there and search for arm-eabi.
[Android Q&A, Help & Troubleshooting] Gokulbalram:
Here you go:
[Android Q&A, Help & Troubleshooting] MasterAwesome:
Great!

Looks great, now set your path to pathToDir/arm-eabi-4.8/bin and then

export ARCH=arm&&export CROSS_COMPILE=arm-eabi-

and then

make defconfig
make zImage

I strongly suggest you create an linux partition instead of a virtual desktop and also suggest you have all your source files on the EXT4 partition since they have particular permissions when repo synced(Not that it's necessary). If i were you, I'd create a seperate linux partition with 100 GiB and sync my source there, now that you have downloaded the source, just transfer the .repo folder into the ext4 partition and do

repo sync -l

I also notice that you're on 9GAG, RESPECT!!! :P
[Android Q&A, Help & Troubleshooting] Gokulbalram:
Thanks for this man. I'm creating a new partition (ext4). I'll report back in 10 minutes.

Yes I am! Here, have a

[IMG="Lol Potato"]http://www.permaculture.co.uk/sites/default/files/images/greek-potato.standard%20460x345.gif[/IMG]

EDIT: My Disk has errors which I'll keep for checking via CHKDSK overnight or something.

And what permissions are you talking about?

---------- Post added at 06:13 PM ---------- Previous post was at 05:13 PM ----------

Is there anyway I can get the source to use a prebuilt kernel?
[Android Q&A, Help & Troubleshooting] domenicogalati45:
Hi guys, can I get a build box space? It is very important. Please

Inviato dal mio ME173X utilizzando Tapatalk
[Android Q&A, Help & Troubleshooting] baselsayeh:
im trying to compile cm12 for gt-s7562

but the linker throws an error

frameworks/av/media/libmediaplayerservice/StagefrightRecorder.cpp:1064: error: undefined reference to 'android::MEDIA_MIMETYPE_AUDIO_EVRC'
frameworks/av/media/libmediaplayerservice/StagefrightRecorder.cpp:2125: error: undefined reference to 'android::FMA2DPWriter::FMA2DPWriter()'
frameworks/av/media/libmediaplayerservice/StagefrightRecorder.cpp:2157: error: undefined reference to 'android::ExtendedWriter::ExtendedWriter(int)'
collect2: error: ld returned 1 exit status

1064:

CHECK(audioSource->getFormat()->findInt32(
kKeyMaxInputSize, &maxInputSize));

device directory

this is the first time compiling cm
[Android Q&A, Help & Troubleshooting] adinkwok:
Has any of the S Duos devs been able to compile CM11 first? I use to have the single sim version of the phone and we were able to get CM10-Omni5.0. Here is the CM11 tree: https://github.com/jonypx09/android_device_samsung_kylessopen. If you can build using this guy's sources, it should boot. Once you get CM11, it isn't that hard to get CM12.
[Android Q&A, Help & Troubleshooting] baselsayeh:
YES there is cm11 with broken things

ill try to compile with those files
[Android Q&A, Help & Troubleshooting] h2o64:
That's a kernel error... (Need VIDC definitions)

You must use the CAF hardware/qcom stuff :)
[Android Q&A, Help & Troubleshooting] hhp_211:
I'm still having this problem with builds

Anyone seen this before?

Link to post:

http://xdaforums.com/showthread.php?p=57570690
[Android Q&A, Help & Troubleshooting] adinkwok:
Hmm... Have you tried updating your manifest? There might have been changes to it (it doesn't get updated in repo sync).
[Android Q&A, Help & Troubleshooting] hhp_211:
I'm up for trying it. This is what I'm using same as in the thread

It seems right, but do you have any suggestions?

I thought about different proprietaries instead of the muppets...

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_oneplus_bacon" path="device/oneplus/bacon" remote="github" />

<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />

<project name="CyanogenMod/android_device_oppo_msm8974-common" path="device/oppo/msm8974-common" remote="github" />

<project name="CyanogenMod/android_device_oppo_common" path="device/oppo/common" remote="github" revision="cm-12.0" />

<project name="CyanogenMod/android_kernel_oneplus_msm8974" path="kernel/oneplus/msm8974" remote="github" />

<project name="TheMuppets/proprietary_vendor_oppo" path="vendor/oppo" remote="github" />

<project name="TheMuppets/proprietary_vendor_oneplus" path="vendor/oneplus" remote="github" />

<project name="CyanogenMod/android_frameworks_opt_connectivity" path="frameworks/opt/connectivity" remote="github" revision="cm-11.0" />
</manifest>

.
[Android Q&A, Help & Troubleshooting] adinkwok:
I was talking about the default.xml :P.
[Android Q&A, Help & Troubleshooting] baselsayeh:
even now there is more errors

device/samsung/kylessopen/libaudio/AudioHardware.cpp: At global scope:
device/samsung/kylessopen/libaudio/AudioHardware.cpp:4018:10: warning: unused parameter 'observer' [-Wunused-parameter]
status_t AudioHardware::AudioSessionOutLPA::setObserver(void *observer)
^
device/samsung/kylessopen/libaudio/AudioHardware.cpp:4048:10: warning: unused parameter 'dspFrames' [-Wunused-parameter]
status_t AudioHardware::AudioSessionOutLPA::getRenderPosition(uint32_t *dspFrames)
^
device/samsung/kylessopen/libaudio/AudioHardware.cpp:4231:10: warning: unused parameter 'args' [-Wunused-parameter]
status_t AudioHardware::AudioStreamInMSM72xx::dump(int fd, const Vector<String16>& args)
^
device/samsung/kylessopen/libaudio/AudioHardware.cpp: In function 'android_audio_legacy::AudioHardwareInterface* android_audio_legacy::createAudioHardware()':
device/samsung/kylessopen/libaudio/AudioHardware.cpp:4300:30: error: cannot allocate an object of abstract type 'android_audio_legacy::AudioHardware'
return new AudioHardware();
^
In file included from device/samsung/kylessopen/libaudio/AudioHardware.cpp:35:0:
device/samsung/kylessopen/libaudio/AudioHardware.h:182:7: note: because the following virtual functions are pure within 'android_audio_legacy::AudioHardware':
class AudioHardware : public AudioHardwareBase
^
In file included from hardware/libhardware_legacy/include/hardware_legacy/AudioHardwareBase.h:20:0,
from device/samsung/kylessopen/libaudio/AudioHardware.h:29,
from device/samsung/kylessopen/libaudio/AudioHardware.cpp:35:
hardware/libhardware_legacy/include/hardware_legacy/AudioHardwareInterface.h:269:29: note:	virtual android_audio_legacy::AudioStreamOut* android_audio_legacy::AudioHardwareInterface::openOutputStreamWithFlags(uint32_t, audio_output_flags_t, int*, uint32_t*, uint32_t*, android::status_t*)
virtual AudioStreamOut* openOutputStreamWithFlags(
^
device/samsung/kylessopen/libaudio/AudioHardware.cpp: In member function 'virtual size_t android_audio_legacy::AudioHardware::getInputBufferSize(uint32_t, int, int)':
device/samsung/kylessopen/libaudio/AudioHardware.cpp:1563:1: error: control reaches end of non-void function [-Werror=return-type]
}
^
device/samsung/kylessopen/libaudio/AudioHardware.cpp: In function 'android_audio_legacy::AudioHardwareInterface* android_audio_legacy::createAudioHardware()':
device/samsung/kylessopen/libaudio/AudioHardware.cpp:4301:1: error: control reaches end of non-void function [-Werror=return-type]
}
^
cc1plus: some warnings being treated as errors
make: *** [/home/basel/Desktop/cm/out/target/product/kylessopen/obj/SHARED_LIBRARIES/audio.primary.msm7x27a_intermediates/AudioHardware.o] Error 1
device/samsung/kylessopen/libaudio/HardwarePinSwitching.c: In function 'switch_mode':
device/samsung/kylessopen/libaudio/HardwarePinSwitching.c:221:29: warning: unused parameter 'nMode' [-Wunused-parameter]
extern int switch_mode( int nMode ) {

http://pastebin.com/8ANRSwGY
[Android Q&A, Help & Troubleshooting] MasterAwesome:
Says some warnings treated as errors. Just give a GCC flag to ignore these warnings. You can suppress all the warnings by adding a -w at the build/core/combo/target_arm.mk and then set it as global cflags. Or specify the error you want to suppress by adding a -Wno flag.
[Android Q&A, Help & Troubleshooting] baselsayeh:
is it ok to continue the build or i must use make clean first?
[Android Q&A, Help & Troubleshooting] MasterAwesome:
Continuing the build won't cause any errors but its always better to make clean first. If it's almost done, id go with continuing the build since make does a pretty good job restoring to state where the build stopped.
[Android Q&A, Help & Troubleshooting] baselsayeh:
even after i added -Wno-error

TARGET_GLOBAL_CFLAGS += -mtune=cortex-a5 -mfpu=neon -mfloat-abi=softfp -Wno-error

TARGET_GLOBAL_CPPFLAGS += -mtune=cortex-a5 -mfpu=neon -mfloat-abi=softfp -Wno-error

i still have warnings treated as errors

http://pastebin.com/e7tkPE7U
[Android Q&A, Help & Troubleshooting] MasterAwesome:
-Wno-error is not a GCC flag. Just add a

-w for this build
[Android Q&A, Help & Troubleshooting] baselsayeh:
so it should be

TARGET_GLOBAL_CFLAGS += -mtune=cortex-a5 -mfpu=neon -mfloat-abi=softfp -w

TARGET_GLOBAL_CPPFLAGS += -mtune=cortex-a5 -mfpu=neon -mfloat-abi=softfp -w
[Android Q&A, Help & Troubleshooting] MasterAwesome:
Just add another line and define it like

TARGET_GLOBAL_CFLAGS += -w
[Android Q&A, Help & Troubleshooting] baselsayeh:
gives same error

cc1plus: some warnings being treated as errors

Edit:after applying some patches this error disappeared

edit2: same message "some warnings being treated as errors "

http://pastebin.com/RH0VYxRz
[Android Q&A, Help & Troubleshooting] baselsayeh:
new errors

http://pastebin.com/hdJ8J2wD

https://github.com/baselsayeh/gt-s7560-cm-device/tree/cm-12/libaudio
[Android Q&A, Help & Troubleshooting] MasterAwesome:
Looks like its either a error caused due to the new GCC 4.8 in cm12 source or its that the CPP is bad. Try individually compiling that module using GCC 4.7 if it works, modify the android.mk in that folder to use 4.7 instead of 4.8 else download eclipse ide and debug it there.