Please don't do that, your build will fail in some other way, since that
check is there to ensure that the two build systems agree about options
that they both need to use.

On Sat, Dec 9, 2017 at 12:58 PM, Blaze Ristov <blazeristo...@gmail.com>
wrote:

> In the file build/soong/android/makevars.go, there are these 3 lines:
>
> ifneq ($(my_check_failed),false)
>   $(error Soong variable check failed)
> endif
>
> Either remove them or just comment out the 2nd line ( # $(error Soong
> variable check failed) )
>
> On Fri, Dec 8, 2017 at 12:46 PM, <q944489...@gmail.com> wrote:
>
>> When I builing the AOSP for my device ,I have a problem that I can't slove
>>
>>
>> home/jack/Mokee/O/out/soong/make_vars-mk_N939St.mk:362: warning:
>> TARGET_GLOBAL_CFLAGS does not match between Make and Soong:
>> /home/jack/Mokee/O/out/soong/make_vars-mk_N939St.mk:362: warning: Make :
>> -DNO_SECURE_DISCARD
>> /home/jack/Mokee/O/out/soong/make_vars-mk_N939St.mk:362: warning: Soong:
>> -fno-exceptions -Wno-multichar -fno-strict-aliasing
>> -fstack-protector-strong -ffunction-sections -fdata-sections
>> -funwind-tables -Wa,--noexecstack -Werror=format-security
>> -D_FORTIFY_SOURCE=2 -fno-short-enums -no-canonical-prefixes
>> -fno-canonical-system-headers -Werror=pointer-to-int-cast
>> -Werror=int-to-pointer-cast -Werror=implicit-function-declaration
>> -fno-strict-volatile-bitfields -DNDEBUG -O2 -g -Wstrict-aliasing=2
>> -fgcse-after-reload -frerun-cse-after-loop -frename-registers -DANDROID
>> -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith
>> -DNDEBUG -UDEBUG -fdebug-prefix-map=/proc/self/cwd= -fdiagnostics-color
>> -Werror=return-type -Werror=non-virtual-dtor -Werror=address
>> -Werror=sequence-point -Werror=date-time -mcpu=cortex-a53
>> /home/jack/Mokee/O/out/soong/make_vars-mk_N939St.mk:810: error: Soong
>> variable check failed.
>> 18:19:38 ckati failed with: exit status 1
>> build/core/main.mk:21: recipe for target 'run_soong_ui' failed
>> make: *** [run_soong_ui] Error 1
>>
>> --
>> --
>> You received this message because you are subscribed to the "Android
>> Building" mailing list.
>> To post to this group, send email to android-building@googlegroups.com
>> To unsubscribe from this group, send email to
>> android-building+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/android-building?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Android Building" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to android-building+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to