[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Please help check one issue with make[3.82] for Android source code

From: Paul Smith
Subject: Re: Please help check one issue with make[3.82] for Android source code build
Date: Fri, 16 Oct 2015 11:58:37 -0400

Please choose just one mailing list to ask your question on, rather than
sending it to multiple lists at a time.

On Fri, 2015-10-16 at 23:18 +0800, liny_pyp wrote:
> Hi:
> I am using Ubuntu(15.04) environment to build the android source code.
> For the android K version, it needs the Make version as 3.81 or 3.82,
> and I used the 3.82 version as below:
> address@hidden:~/mine/$ make --version
> GNU Make 3.82
> Built for x86_64-unknown-linux-gnu
> Copyright (C) 2010  Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> But I got two build error caused by Make seems doesn't support some
> feature such as '-=' or the define feature, could you help check it
> and tell me how make can support these function? Thanks a lot for your
> help.

> Scenario 1:
> Makefile:
> 116 ifeq ($(LLVM_VER_31), 1)
> 119 endif

There's no such operator as "-=" in any version of GNU make, past,
present, or future.  This is is a syntax error.

> Error:
> sc/sc.srcs.mk:117: *** missing separator.  Stop.
> Scenario 2:
> Makefile:
>  12 libmmipl_cflags := -g -O3 \
>  13         $(CPU)
>  14         -Dlrintf=_ffix_r \
>  15         -D__alignx\(x\)=__attribute__\(\(__aligned__\(x\)\)\)
>  16         -D_POSIX_SOURCE \
>  17         -DPOSIX_C_SOURCE=199506L \
> Error:
> ipl/Android.mk:16: *** recipe commences before first target.  Stop.

This is also a syntax error (missing backslash at the end of line 13).

Neither of these issues are related to GNU make (or any other GNU
utils).  It's simply the case that these are invalid GNU makefiles.
Either you have accidentally modified them to be invalid in which case
don't do that :), or else they are being shipped that way in which case
you should contact the package maintainers for this source code and ask
them to fix these problems.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]