From: Rongqing Li <rongqing.li@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH][v4] mmc-utils: fix the building failure when DEBUG_BUILD is 1
Date: Wed, 24 Jun 2015 09:42:09 +0800 [thread overview]
Message-ID: <558A0AF1.8060204@windriver.com> (raw)
In-Reply-To: <CAJTo0LZxzFL=DHq9NxVvcs=VNmPnCe=Z2V6ksAaBmLQ0+FAHxQ@mail.gmail.com>
On 2015年06月23日 19:23, Burton, Ross wrote:
>
> On 3 June 2015 at 02:24, <rongqing.li@windriver.com
> <mailto:rongqing.li@windriver.com>> wrote:
>
> +CFLAGS += "-U_FORTIFY_SOURCE"
>
>
> So Richard made the valid point that this is disabling the security
> flags in mmc-utils globally to fix builds in the very few cases when
> DEBUG_BUILD is enabled.
>
> Would it be sensible to have an include file that enables DEBUG_BUILD
> and also tweaks CFLAGS where required? I'd also like to see what the
> error is, and if it can be fixed in the code for good instead.
>
> Ross
1. configuration
rli2@pek-hostel-deb02:/buildarea1/lirq/Yocto/poky/build$ tail -n1
conf/local.conf
SELECTED_OPTIMIZATION = " -O0 "
rli2@pek-hostel-deb02:/buildarea1/lirq/Yocto/poky/build$
2. the error
NOTE: Preparing RunQueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: do_compile (log file is located at
/buildarea1/lirq/Yocto/poky/build/tmp/work/armv5e-poky-linux-gnueabi/mmc-utils/0.1-r0/temp/log.do_compile.30117)
ERROR: Logfile of failure stored in:
/buildarea1/lirq/Yocto/poky/build/tmp/work/armv5e-poky-linux-gnueabi/mmc-utils/0.1-r0/temp/log.do_compile.30117
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 24 -e MAKEFLAGS=
| arm-poky-linux-gnueabi-gcc -march=armv5e -marm -mthumb-interwork
--sysroot=/buildarea1/lirq/Yocto/poky/build/tmp/sysroots/qemuarm -Wall
-Werror -Wuninitialized -Wundef -D_FILE_OFFSET_BITS=64
-D_FORTIFY_SOURCE=2 -O0 -Wp,-MMD,./.mmc.o.d,-MT,mmc.o -c mmc.c -o mmc.o
| arm-poky-linux-gnueabi-gcc -march=armv5e -marm -mthumb-interwork
--sysroot=/buildarea1/lirq/Yocto/poky/build/tmp/sysroots/qemuarm -Wall
-Werror -Wuninitialized -Wundef -D_FILE_OFFSET_BITS=64
-D_FORTIFY_SOURCE=2 -O0 -Wp,-MMD,./.mmc_cmds.o.d,-MT,mmc_cmds.o -c
mmc_cmds.c -o mmc_cmds.o
| arm-poky-linux-gnueabi-gcc -march=armv5e -marm -mthumb-interwork
--sysroot=/buildarea1/lirq/Yocto/poky/build/tmp/sysroots/qemuarm -Wall
-Werror -Wuninitialized -Wundef -D_FILE_OFFSET_BITS=64
-D_FORTIFY_SOURCE=2 -O0
-Wp,-MMD,3rdparty/hmac_sha/.hmac_sha2.o.d,-MT,3rdparty/hmac_sha/hmac_sha2.o
-c 3rdparty/hmac_sha/hmac_sha2.c -o 3rdparty/hmac_sha/hmac_sha2.o
| arm-poky-linux-gnueabi-gcc -march=armv5e -marm -mthumb-interwork
--sysroot=/buildarea1/lirq/Yocto/poky/build/tmp/sysroots/qemuarm -Wall
-Werror -Wuninitialized -Wundef -D_FILE_OFFSET_BITS=64
-D_FORTIFY_SOURCE=2 -O0
-Wp,-MMD,3rdparty/hmac_sha/.sha2.o.d,-MT,3rdparty/hmac_sha/sha2.o -c
3rdparty/hmac_sha/sha2.c -o 3rdparty/hmac_sha/sha2.o
| make -C man
| make[1]: Entering directory
`/buildarea1/lirq/Yocto/poky/build/tmp/work/armv5e-poky-linux-gnueabi/mmc-utils/0.1-r0/git/man'
| make[1]: Nothing to be done for `all'.
| make[1]: Leaving directory
`/buildarea1/lirq/Yocto/poky/build/tmp/work/armv5e-poky-linux-gnueabi/mmc-utils/0.1-r0/git/man'
| In file included from
/buildarea1/lirq/Yocto/poky/build/tmp/sysroots/qemuarm/usr/include/stdio.h:27:0,
| from mmc.c:20:
|
/buildarea1/lirq/Yocto/poky/build/tmp/sysroots/qemuarm/usr/include/features.h:328:4:
error: #warning _FORTIFY_SOURCE requires compiling with optimization
(-O) [-Werror=cpp]
| # warning _FORTIFY_SOURCE requires compiling with optimization (-O)
| ^
| In file included from
/buildarea1/lirq/Yocto/poky/build/tmp/sysroots/qemuarm/usr/include/string.h:25:0,
| from 3rdparty/hmac_sha/hmac_sha2.c:38:
|
/buildarea1/lirq/Yocto/poky/build/tmp/sysroots/qemuarm/usr/include/features.h:328:4:
error: #warning _FORTIFY_SOURCE requires compiling with optimization
(-O) [-Werror=cpp]
| # warning _FORTIFY_SOURCE requires compiling with optimization (-O)
| ^
| In file included from
/buildarea1/lirq/Yocto/poky/build/tmp/sysroots/qemuarm/usr/include/stdio.h:27:0,
| from mmc_cmds.c:17:
|
/buildarea1/lirq/Yocto/poky/build/tmp/sysroots/qemuarm/usr/include/features.h:328:4:
error: #warning _FORTIFY_SOURCE requires compiling with optimization
(-O) [-Werror=cpp]
| # warning _FORTIFY_SOURCE requires compiling with optimization (-O)
| ^
| In file included from
/buildarea1/lirq/Yocto/poky/build/tmp/sysroots/qemuarm/usr/include/string.h:25:0,
| from 3rdparty/hmac_sha/sha2.c:42:
|
/buildarea1/lirq/Yocto/poky/build/tmp/sysroots/qemuarm/usr/include/features.h:328:4:
error: #warning _FORTIFY_SOURCE requires compiling with optimization
(-O) [-Werror=cpp]
| # warning _FORTIFY_SOURCE requires compiling with optimization (-O)
| ^
| cc1: all warnings being treated as errors
| make: *** [3rdparty/hmac_sha/hmac_sha2.o] Error 1
| make: *** Waiting for unfinished jobs....
| cc1: all warnings being treated as errors
| make: *** [mmc.o] Error 1
| cc1: all warnings being treated as errors
| make: *** [3rdparty/hmac_sha/sha2.o] Error 1
| cc1: all warnings being treated as errors
| make: *** [mmc_cmds.o] Error 1
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at
/buildarea1/lirq/Yocto/poky/build/tmp/work/armv5e-poky-linux-gnueabi/mmc-utils/0.1-r0/temp/log.do_compile.30117)
ERROR: Task 6
(/buildarea1/lirq/Yocto/poky/meta/recipes-devtools/mmc/mmc-utils_git.bb,
do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 362 tasks of which 294 didn't need to be
rerun and 1 failed.
Waiting for 0 running tasks to finish:
-R
next prev parent reply other threads:[~2015-06-24 1:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 1:24 [PATCH][v4] mmc-utils: fix the building failure when DEBUG_BUILD is 1 rongqing.li
2015-06-10 8:58 ` Rongqing Li
2015-06-18 9:12 ` Rongqing Li
2015-06-23 11:23 ` Burton, Ross
2015-06-24 1:42 ` Rongqing Li [this message]
2015-06-24 14:16 ` Burton, Ross
2015-06-25 6:59 ` Rongqing Li
2015-06-25 9:30 ` Burton, Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=558A0AF1.8060204@windriver.com \
--to=rongqing.li@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox