elfutils cc1: all warnings being treated as errors
/**********************************************************************
* elfutils cc1: all warnings being treated as errors
* 说明:
* 在Ubuntu 18.04上编译Yocto,elfutils的Makefile中出现没有识别到一些配置,
* 需要在Makefile中去掉-Werror选项。
*
* 2018-6-14 深圳 宝安西乡 曾剑锋
*********************************************************************/ 一、参考文档:
. How to compile without warnings being treated as errors?
https://stackoverflow.com/questions/11561261/how-to-compile-without-warnings-being-treated-as-errors
. all warnings being treated as errors
https://wizardforcel.gitbooks.io/100-gcc-tips/content/warnings-treated-as-errors.html 二、报错现象:
. 现象:
x86_64-linux/usr/include -O2 -pipe -c -o dwfl_report_elf.o ../../elfutils-0.164/libdwfl/dwfl_report_elf.c
| ../../elfutils-0.164/libdwfl/dwfl_report_elf.c: In function '__libdwfl_elf_address_range':
| ../../elfutils-0.164/libdwfl/dwfl_report_elf.c::: error: this statement may fall through [-Werror=implicit-fallthrough=]
| add_p_vaddr = true;
| ^
| ../../elfutils-0.164/libdwfl/dwfl_report_elf.c::: note: here
| case ET_DYN:
| ^~~~
| cc1: all warnings being treated as errors
| Makefile:: recipe for target 'dwfl_report_elf.o' failed
. 现象:
imx6q-x11/tmp/sysroots/x86_64-linux/usr/include -O2 -pipe -c -o dwarf_next_cfi.o ../../elfutils-0.164/libdw/dwarf_next_cfi.c
| In file included from ../../elfutils-0.164/libdw/dwarf_next_cfi.c:::
| ../../elfutils-0.164/libdw/encoded-value.h: In function 'encoded_value_size':
| ../../elfutils-0.164/libdw/encoded-value.h::: error: this statement may fall through [-Werror=implicit-fallthrough=]
| if (p != NULL)
| ^
| ../../elfutils-0.164/libdw/encoded-value.h::: note: here
| default:
| ^~~~~~~
| cc1: all warnings being treated as errors
| Makefile:: recipe for target 'dwarf_next_cfi.o' failed
| make[]: *** [dwarf_next_cfi.o] Error
. 现象:
inux/usr/include -O2 -pipe -c -o i386_disasm.o ../../elfutils-0.164/libcpu/i386_disasm.c
| ../../elfutils-0.164/libcpu/i386_disasm.c: In function 'i386_disasm':
| ../../elfutils-0.164/libcpu/i386_disasm.c::: error: this statement may fall through [-Werror=implicit-fallthrough=]
| if (data[] == 0xc2)
| ^
| ../../elfutils-0.164/libcpu/i386_disasm.c::: note: here
| default:
| ^~~~~~~
| cc1: all warnings being treated as errors
| Makefile:: recipe for target 'i386_disasm.o' failed 三、解决方法:
. 原因: cc1: all warnings being treated as errors
. 修改对应的Makefile,去掉-Werror:
. 手动处理示例:
/home/zengjf/zengjf/fsl-release-bsp/imx6q-x11/tmp/work/x86_64-linux/elfutils-native/0.164-r0/build/libdwfl/Makefile
[...省略]
# Warn about stack usage of more than 256K = bytes.
STACK_USAGE_WARNING = -Wstack-usage=
AM_CFLAGS = -std=gnu99 -Wall -Wshadow -Wformat= \
-Wold-style-definition -Wstrict-prototypes \
$(if $($(*F)_no_Werror),,-Werror) \ # remove this line
$(if $($(*F)_no_Wunused),,-Wunused -Wextra) \
$(if $($(*F)_no_Wstack_usage),,$(STACK_USAGE_WARNING)) \
$($(*F)_CFLAGS)
[...省略]
. 获取Makefile生成信息:
zengjf@zengjf:~/zengjf/fsl-release-bsp/imx6q-x11/tmp/work/x86_64-linux/elfutils-native/0.164-r0$ grep _no_Werror * -r
build/tests/Makefile: $(if $($(*F)_no_Werror),,-Werror) \
build/libdwfl/Makefile.bak: $(if $($(*F)_no_Werror),,-Werror) \
build/backends/Makefile: $(if $($(*F)_no_Werror),,-Werror) \
build/libdwelf/Makefile: $(if $($(*F)_no_Werror),,-Werror) \
build/lib/Makefile: $($(*F)_no_Werror),,-Werror) $(if \
build/libasm/Makefile: $(if $($(*F)_no_Werror),,-Werror) \
build/libelf/Makefile: $($(*F)_no_Werror),,-Werror) $(if \
build/libebl/Makefile: $($(*F)_no_Werror),,-Werror) $(if \
build/src/Makefile: $(if $($(*F)_no_Werror),,-Werror) \
build/src/Makefile:ldlex_no_Werror = yes
build/libcpu/Makefile:i386_lex_no_Werror = yes
elfutils-0.164/tests/Makefile.in: $(if $($(*F)_no_Werror),,-Werror) \
elfutils-0.164/libdwfl/Makefile.in: $(if $($(*F)_no_Werror),,-Werror) \
elfutils-0.164/backends/Makefile.in: $(if $($(*F)_no_Werror),,-Werror) \
elfutils-0.164/config/eu.am: $(if $($(*F)_no_Werror),,-Werror) \
elfutils-0.164/libdwelf/Makefile.in: $(if $($(*F)_no_Werror),,-Werror) \
elfutils-0.164/libdw/Makefile.in: $($(*F)_no_Werror),,-Werror) $(if \
elfutils-0.164/lib/Makefile.in: $($(*F)_no_Werror),,-Werror) $(if \
elfutils-0.164/libasm/Makefile.in: $(if $($(*F)_no_Werror),,-Werror) \
elfutils-0.164/libelf/Makefile.in: $($(*F)_no_Werror),,-Werror) $(if \
elfutils-0.164/libebl/Makefile.in: $($(*F)_no_Werror),,-Werror) $(if \
elfutils-0.164/src/Makefile.in: $(if $($(*F)_no_Werror),,-Werror) \
elfutils-0.164/src/Makefile.in:ldlex_no_Werror = yes
elfutils-0.164/src/Makefile.am:ldlex_no_Werror = yes
elfutils-0.164/libcpu/Makefile.in: $($(*F)_no_Werror),,-Werror) $(if \
elfutils-0.164/libcpu/Makefile.in:i386_lex_no_Werror = yes
elfutils-0.164/libcpu/Makefile.am:i386_lex_no_Werror = yes
elfutils-0.164/.pc/dso-link-change.patch/src/Makefile.am:ldlex_no_Werror = yes
elfutils-0.164/.pc/uclibc-support.patch/libcpu/Makefile.am:i386_lex_no_Werror = yes
zengjf@zengjf:~/zengjf/fsl-release-bsp/imx6q-x11/tmp/work/x86_64-linux/elfutils-native/0.164-r0$
. 一个一个文件修改比较麻烦,依据第4点,修改对应的yes为no就可以比较快捷的一次性全部解决问题,然而实际情况是没有识别到ldlex和i386_lex,乖乖的手动删除或者制作Shell脚本处理;
. 自动化shell命令:
. grep _no_Werror\) * -r | cut -d":" -f1 | xargs sed -i "s/[$](if [$]([$]([*F]*)_no_Werror),,-Werror)//"
. grep _no_Werror\) * -r | cut -d":" -f1 | xargs sed -i "s/[$]([$]([*F]*)_no_Werror),,-Werror) [$](if//"
elfutils cc1: all warnings being treated as errors的更多相关文章
- gcc cc1: all warnings being treated as errors
cc1: all warnings being treated as errors 在Makefile中找到 -Werror项,删除即可.删除后重新编译. 或设置环境变量 c工程设置 export C ...
- GCC警告提示错误“cc1:all warnings being treated as errors”
http://blog.csdn.net/zhangjs0322/article/details/25131787
- cc1: warnings being treated as errors解决办法
安装GDB时出现cc1: warnings being treated as errors Edit the Makefile and delete this line:WERROR_CFLAGS = ...
- 编译openwrt时报错:fstools-2018-01-02-11efbf3b/libfstools/overlay.c: At top level: cc1: error: unrecognized command line option '-Wno-format-truncation' [-Werror]
1. 详细错误信息 [ 11%] Building C object CMakeFiles/fstools.dir/libfstools/overlay.c.o/home/jello/openwrt/ ...
- ubuntu14.0 (arm平台)源码安装 VLC播放器
环境 ubuntu14.0 arm开发板 源 deb http://mirrors.ustc.edu.cn/ubuntu-ports/ trusty main multiverse restrict ...
- Android编译环境折腾记
题记:感觉是时候写点什么了=_=! 第一次安装了ubuntu14.04.5,官网下载的iso,官网下的jar,编译android4.x需要安装jdk6,更高的版本会有问题,baidu到很多搭建环境的步 ...
- Linux centOS下搭建RTMP服务器的具体步骤
以下的所需的安装包,可直接在linux系统终端下载,也可从其他地方下载之后拷到对应目录下解压使用,遇到连接不到国外网站时可改变压缩包地址 1.安装依赖包: #yum install glibc.i68 ...
- ubuntu下编译VLC
ubuntu下编译VLC 标签(空格分隔): ubuntu vlc 视频 编译 [TOC] 1.下载VLC源码包并解压 VLC的源码包在VLC的官网有,可以直接下载.也可以使用git来clone一个. ...
- SystemTap知识(二)
Unbuntu安装systemtap: http://www.cnblogs.com/hdflzh/archive/2012/07/25/2608910.html 1 更新源到http://mirro ...
随机推荐
- Jmeter4.0----录制脚本
1.前言 Jmeter录制脚本有两种方式.1.通过第三方工具录制比如:Badboy,然后转化为jmeter可用的脚本:2.使用jmeter本身自带的录制脚本功能. 对于测试小白来说可用先使用jmete ...
- spring多个AOP执行先后顺序(面试问题:怎么控制多个aop的执行循序)
转载:spring多个AOP执行先后顺序(面试问题:怎么控制多个aop的执行循序) 众所周知,spring声明式事务是基于AOP实现的,那么,如果我们在同一个方法自定义多个AOP,我们如何指定他们的执 ...
- 窗体应用程序防腾讯QQ源码
窗体应用程序防腾讯QQ源码 using System; using System.Collections.Generic; using System.ComponentModel; using Sys ...
- select * from dim.dim_area_no@to_dw
应该是建的有database linksdim是用户名,dim_area_no是表名,to_dw 是建的database links的名,dim_area_no表属于dim用户创建database l ...
- break&&continue
break和continue的区别: 1. 当它们用在循环语句的循环体时,break用于立即退出本层循环,而continue仅仅结束本次循环(本次循环体内不执行continue语句后的其它语句,但下一 ...
- learning scala control statement
1 .if satement 与其它语言不同的是,scala if statement 返回的是一个值 scala> val a = if ( 6 > 0 ) 1 else -1a: In ...
- MFC Release版本串口连不上的问题
项目开发过程中发现Release版本存在连接串口时,第一次开机后,出现连接不上的问题,但在Debug版本下正常:而且只要连接上一次,Release版本就能正常连接: 解决方案: 在串口配置过程中更改为 ...
- DevExpress ASP.NET Bootstrap Controls v18.2新功能详解(二)
行业领先的.NET界面控件2018年第二次重大更新——DevExpress v18.2日前正式发布,本站将以连载的形式为大家介绍新版本新功能.本文将介绍了DevExpress ASP.NET Boot ...
- SharePoint REST API - 文件夹和文件
博客地址:http://blog.csdn.net/FoxDave 本篇讲述如何通过REST操作文件夹和文件. 使用REST操作文件夹 在你知道某个文档库中的文件夹的URL时,可以使用如下的代码获 ...
- 内存布局:栈,堆,BSS段(静态区),代码段,数据段
简介 我们程序运行的时候都是放在内存里的.根据静态.成员函数.代码段.对象.等等.放在不同的内存分块里.大概分为5块 1 栈 2 堆 3 BSS段-全局区-(静态区) 4 代码段 5 数据段 栈 ...