Re: Re[v2]: Use of GCC plugin instead ISO C
On 03/06/2018 10:01 PM, Progyan Bhattacharya wrote: > On Tue, 2018-03-06 at 09:24 -0800, Randy Dunlap wrote: >> First, please make sure that this file does not already exist before >> starting >> a build: /home/progyan/Programs/Linux/tools/objtool/.objtool- >> in.o.cmd > > Yes, it was there and I removed it. > >> Then I will look at this more if you will send me your kernel .config >> file and >> the exact command(s) that you use to run the build. I'm still not seeing any problems. > I am running build by: > make V=1 That's all? anything after the "V=1"? > > Here is my config and build log this time. > /bin/sh: scripts/genksyms/modules.order: Permission denied To me that message most likely means that the file is present in your O= directory, but that it is owned by someone else (possibly root). Can you remove everything in the O= directory (rm -rf ; mkdir ) and then try again? -- ~Randy
Re: Re[v2]: Use of GCC plugin instead ISO C
On 03/06/2018 05:28 AM, Progyan Bhattacharya wrote: > On Thu, 2018-03-01 at 13:42 -0800, Randy Dunlap wrote: >> If you would build with V=1 and capture all of the output (lots of >> it!) to a file, >> you could search it for "pedantic" to see where/why it is used. >> >> I have no idea about the permission problem that you quoted above. > > Sorry for the misunderstanding! > Here is the full build log for > > make V=1 > Thanks. I don't see a problem there except for the final line. First, please make sure that this file does not already exist before starting a build: /home/progyan/Programs/Linux/tools/objtool/.objtool-in.o.cmd Then I will look at this more if you will send me your kernel .config file and the exact command(s) that you use to run the build. thanks, -- ~Randy
Re: Re[v2]: Use of GCC plugin instead ISO C
On Thu, 2018-03-01 at 13:42 -0800, Randy Dunlap wrote: > If you would build with V=1 and capture all of the output (lots of > it!) to a file, > you could search it for "pedantic" to see where/why it is used. > > I have no idea about the permission problem that you quoted above. Sorry for the misunderstanding! Here is the full build log for make V=1 -- Regards, Progyan Bhattacharya (http://codeprogyan.me)make -f ./Makefile silentoldconfig make -f ./scripts/Makefile.build obj=scripts/basic (cat /dev/null; ) > scripts/basic/modules.order rm -f .tmp_quiet_recordmcount make -f ./scripts/Makefile.build obj=scripts/kconfig silentoldconfig mkdir -p include/config include/generated test -e include/generated/autoksyms.h || \ touch include/generated/autoksyms.h scripts/kconfig/conf --silentoldconfig Kconfig make -f ./scripts/Makefile.build obj=arch/x86/entry/syscalls all make -f ./scripts/Makefile.build obj=scripts/basic (cat /dev/null; ) > scripts/basic/modules.order rm -f .tmp_quiet_recordmcount make -f ./scripts/Makefile.build obj=arch/x86/tools relocs set -e; : ' CHK include/config/kernel.release'; mkdir -p include/config/; echo "4.16.0-rc4$(/bin/sh ./scripts/setlocalversion .)" < include/config/auto.conf > include/config/kernel.release.tmp; if [ -r include/config/kernel.release ] && cmp -s include/config/kernel.release include/config/kernel.release.tmp; then rm -f include/config/kernel.release.tmp; else : ' UPD include/config/kernel.release'; mv -f include/config/kernel.release.tmp include/config/kernel.release; fi make -f ./scripts/Makefile.asm-generic \ src=uapi/asm obj=arch/x86/include/generated/uapi/asm make -f ./scripts/Makefile.asm-generic \ src=asm obj=arch/x86/include/generated/asm set -e; : ' CHK include/generated/uapi/linux/version.h'; mkdir -p include/generated/uapi/linux/; (echo \#define LINUX_VERSION_CODE 266240; echo '#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))';) < Makefile > include/generated/uapi/linux/version.h.tmp; if [ -r include/generated/uapi/linux/version.h ] && cmp -s include/generated/uapi/linux/version.h include/generated/uapi/linux/version.h.tmp; then rm -f include/generated/uapi/linux/version.h.tmp; else : ' UPD include/generated/uapi/linux/version.h'; mv -f include/generated/uapi/linux/version.h.tmp include/generated/uapi/linux/version.h; fi rm -f include/linux/version.h set -e; : ' CHK include/generated/utsrelease.h'; mkdir -p include/generated/; if [ `echo -n "4.16.0-rc4+" | wc -c ` -gt 64 ]; then echo '"4.16.0-rc4+" exceeds 64 characters' >&2; exit 1; fi; (echo \#define UTS_RELEASE \"4.16.0-rc4+\";) < include/config/kernel.release > include/generated/utsrelease.h.tmp; if [ -r include/generated/utsrelease.h ] && cmp -s include/generated/utsrelease.h include/generated/utsrelease.h.tmp; then rm -f include/generated/utsrelease.h.tmp; else : ' UPD include/generated/utsrelease.h'; mv -f include/generated/utsrelease.h.tmp include/generated/utsrelease.h; fi mkdir -p .tmp_versions ; rm -f .tmp_versions/* make -f ./scripts/Makefile.build obj=arch/x86/purgatory arch/x86/purgatory/kexec-purgatory.c gcc -Wp,-MD,arch/x86/purgatory/.purgatory.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/4.8.5/include -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -D__KERNEL__ -DCONFIG_CC_STACKPROTECTOR -fno-strict-aliasing -Wall -Wstrict-prototypes -fno-zero-initialized-in-bss -fno-builtin -ffreestanding -c -MD -Os -mcmodel=large -m64 -fno-PIE -DKBUILD_BASENAME='"purgatory"' -DKBUILD_MODNAME='"purgatory"' -c -o arch/x86/purgatory/.tmp_purgatory.o arch/x86/purgatory/purgatory.c if [ "" = "-pg" ]; then if [ arch/x86/purgatory/purgatory.o != "scripts/mod/empty.o" ]; then ./scripts/recordmcount "arch/x86/purgatory/purgatory.o"; fi; fi; gcc -Wp,-MD,arch/x86/purgatory/.sha256.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/4.8.5/include -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -D__KERNEL__ -DCONFIG_CC_STACKPROTECTOR -fno-strict-aliasing -Wall -Wstrict-prototypes -fno-zero-initialized-in-bss -fno-builtin -ffreestanding -c -MD -Os -mcmodel=large -m64 -fno-PIE -DKBUILD_BASENAME='"sha256"' -DKBUILD_MODNAME='"sha256"' -c -o arch/x86/purgatory/.tmp_sha256.o arch/x86/purgatory/sha256.c if [ "" = "-pg" ]; then if [ arch/x86/purgatory/sha256.o != "scripts/mod/empty.o" ]; then ./scripts/recordmcount "arch/x86/purgatory/sha256.o"; fi; fi; gcc -Wp,-MD,arch/x86/purgatory/.string.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/4.8.5/include -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/inclu
Re: Re[v2]: Use of GCC plugin instead ISO C
On 02/28/2018 11:50 PM, Progyan Bhattacharya wrote: > On Thu, 2018-02-22 at 20:07 +0530, Progyan Bhattacharya wrote: >> On Sun, 2018-02-18 at 08:47 -0800, Randy Dunlap wrote: >>> You could try (re)building with V=1 on the "make" command line and >>> capture >>> the output to see where the "pedantic" is coming from. >> >> This is a late reply. >> I did what you told me and the build failed at following point: >> >> /bin/sh: /home/progyan/Programs/Linux/tools/objtool/.objtool- >> in.o.cmd: Permission denied >> >> I am not sure what permission it wants or what to make of it. >> >> Thanks in advance. Is that a question? I don't get or see that message. What distro are you using? Maybe it adds some build options? If you would build with V=1 and capture all of the output (lots of it!) to a file, you could search it for "pedantic" to see where/why it is used. I have no idea about the permission problem that you quoted above. -- ~Randy
Re[v2]: Use of GCC plugin instead ISO C
On Thu, 2018-02-22 at 20:07 +0530, Progyan Bhattacharya wrote: > On Sun, 2018-02-18 at 08:47 -0800, Randy Dunlap wrote: > > You could try (re)building with V=1 on the "make" command line and > > capture > > the output to see where the "pedantic" is coming from. > > This is a late reply. > I did what you told me and the build failed at following point: > > /bin/sh: /home/progyan/Programs/Linux/tools/objtool/.objtool- > in.o.cmd: Permission denied > > I am not sure what permission it wants or what to make of it. > > Thanks in advance. -- Regards, Progyan Bhattacharya (http://codeprogyan.me)
Re: Use of GCC plugin instead ISO C
On Sun, 2018-02-18 at 08:47 -0800, Randy Dunlap wrote: > You could try (re)building with V=1 on the "make" command line and > capture > the output to see where the "pedantic" is coming from. This is a late reply. I did what you told me and the build failed at following point: /bin/sh: /home/progyan/Programs/Linux/tools/objtool/.objtool- in.o.cmd: Permission denied I am not sure what permission it wants or what to make of it. Thanks in advance. -- Regards, Progyan Bhattacharya (http://codeprogyan.me)
Re: Use of GCC plugin instead ISO C
On 02/18/2018 12:06 AM, Progyan Bhattacharya wrote: > Hi Again, > > According to last time talked, you said me to avoid "-Werror=pedantic" > flag to build the GNU specific plugins instead of Standard ISO C. I > changed my default compiler flags and tried to rebuild. But I am still > getting the same error messages at: > > CC /***/Linux/tools/objtool/arch/x86/decode.o > > All of them were arising due to same "-pedantic" flag being enabled. > 1. Range expression in Case statements were not allowed. > 2. Use of braced-group were not allowed in MACRO definition. > 3. Pointer arithmetic with void pointer was not allowed. > > I took a look on related Makefiles, but found none with "-pedantic" or > "-Werror=pedantic" flag. I didn't find "pedantic" in any Makefiles either. You could try (re)building with V=1 on the "make" command line and capture the output to see where the "pedantic" is coming from. -- ~Randy
Use of GCC plugin instead ISO C
Hi Again, According to last time talked, you said me to avoid "-Werror=pedantic" flag to build the GNU specific plugins instead of Standard ISO C. I changed my default compiler flags and tried to rebuild. But I am still getting the same error messages at: CC /***/Linux/tools/objtool/arch/x86/decode.o All of them were arising due to same "-pedantic" flag being enabled. 1. Range expression in Case statements were not allowed. 2. Use of braced-group were not allowed in MACRO definition. 3. Pointer arithmetic with void pointer was not allowed. I took a look on related Makefiles, but found none with "-pedantic" or "-Werror=pedantic" flag. Flags I found being used in compilation so far, tools/objtool/Makefile: -Wall -Werror -Wno-switch-default -Wno-switch-enum -Wno-packed tools/scripts/Makefile.include: -Wbad-function-cast -Wdeclaration-after-statement -Wformat- security -Wformat-y2k -Winit-self -Wmissing-declarations -Wmissing- prototypes -Wnested-externs -Wno-system-headers -Wold-style-definition -Wpacked -Wredundant-decls -Wshadow -Wstrict-prototypes -Wswitch- default -Wswitch-enum -Wundef -Wwrite-strings -Wformat Compiler I am using: gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) Thanks in advance. -- Regards, Progyan Bhattacharya (http://codeprogyan.me)
