search for: genksym

.../FilesFoundDotC [wild-bill at wlmlfs08 tmp]$ sh ./MakeBugReportData findutils-4.1.20-7.el4.1.i386 88 /tmp/FilesGreppedDotCmd 0 /tmp/FilesFoundDotCmd 3582 /tmp/FilesGreppedDotC 3582 /tmp/FilesFoundDotC 7252 total $ head -5 FilesGreppedDotCmd ./kernels/2.6.9-42.0.2.EL-smp-i686/scripts/genksyms/.genksyms.o.cmd ./kernels/2.6.9-42.0.2.EL-smp-i686/scripts/genksyms/.parse.o.cmd ./kernels/2.6.9-42.0.2.EL-smp-i686/scripts/genksyms/.lex.o.cmd ./kernels/2.6.9-42.0.2.EL-smp-i686/scripts/genksyms/.genksyms.cmd ./kernels/2.6.9-42.0.2.EL-smp-i686/scripts/.conmakehash.cmd TIA -- Bill

I built and installed Lustre from source. When I installed built luster-modules- RPM, I got libcfs.ko from the kernel-2.6.18-prep has no modversions (the message is posted below), so it cannot be reused for kernel. Is there any procedure I need to do during the build? There is include/config/modversion.h under patched kernel, but the file does not have any contens and its size is 0. Thanks for

Hi Can someone help me figure out a way to compile a 2.4 kernel in a 2.6 system. Basically it keeps failing because it needs the genksyms package, which is provided in the modutils package from redhat, but obviously this isn''t presetn on the 2.6 kernel. I was wondering how the xen maintainers go about compiling their 2.4 kernel and 2.6 kernel. Do you do it on different systems then package it together? Thanks Shaz ______...

...nux > > 17385678 5064780 1953892 24404350 174617e defconfig-build/vmlinux > > > > Which shows we inline more (look for asm_volatile for the actual > > changes). > [] > > scripts/checkpatch.pl | 8 ++--- > > scripts/genksyms/keywords.c | 4 +-- > > scripts/kernel-doc | 4 +-- > > I believe these should be excluded from the conversions. Probably, yes. It compiled, which was all I cared about :-) BTW, if we do that conversion, we should upgrade the c...

...nux > > 17385678 5064780 1953892 24404350 174617e defconfig-build/vmlinux > > > > Which shows we inline more (look for asm_volatile for the actual > > changes). > [] > > scripts/checkpatch.pl | 8 ++--- > > scripts/genksyms/keywords.c | 4 +-- > > scripts/kernel-doc | 4 +-- > > I believe these should be excluded from the conversions. Probably, yes. It compiled, which was all I cared about :-) BTW, if we do that conversion, we should upgrade the c...

On Wed, Oct 10, 2018 at 01:54:33PM -0500, Segher Boessenkool wrote: > It would be great to hear from kernel people if it works adequately for > what you guys want it for :-) Sure, ping me when you have the final version and I'll try to build gcc with it and do some size comparisons. Thx. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the

On Wed, Oct 10, 2018 at 01:54:33PM -0500, Segher Boessenkool wrote: > It would be great to hear from kernel people if it works adequately for > what you guys want it for :-) Sure, ping me when you have the final version and I'll try to build gcc with it and do some size comparisons. Thx. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the

...1745f8f defconfig-build/vmlinux > 17385678 5064780 1953892 24404350 174617e defconfig-build/vmlinux > > Which shows we inline more (look for asm_volatile for the actual > changes). [] > scripts/checkpatch.pl | 8 ++--- > scripts/genksyms/keywords.c | 4 +-- > scripts/kernel-doc | 4 +-- I believe these should be excluded from the conversions. Other than that, generic conversion by script seems a good idea.

...5064780 1953892 24404350 174617e defconfig-build/vmlinux > > > > > > Which shows we inline more (look for asm_volatile for the actual > > > changes). > > [] > > > scripts/checkpatch.pl | 8 ++--- > > > scripts/genksyms/keywords.c | 4 +-- > > > scripts/kernel-doc | 4 +-- > > > > I believe these should be excluded from the conversions. > > Probably, yes. It compiled, which was all I cared about :-) > > BTW, if we do that...

...line|noinline|__inline|__inline__}; scripts/checkpatch.pl:# Check for __inline__ and __inline, prefer inline scripts/checkpatch.pl: $line =~ /\b(__inline__|__inline)\b/) { scripts/checkpatch.pl: $fixed[$fixlinenr] =~ s/\b(__inline__|__inline)\b/inline/; scripts/genksyms/keywords.c: { "__inline", INLINE_KEYW }, scripts/kernel-doc: $prototype =~ s/^__inline +//; So all of these could be removed/updated appropriately too

...-rwxr-xr-x 1 root root 47944 31. Mai 2003 cfdisk [... normal entries salvaged] -rwxr-xr-x 1 root root 413 29. Mai 2002 fsck.nfs lrwxrwxrwx 1 root root 7 20. Feb 2003 fsck.vfat -> dosfsck ?rwxrw-rwt 13639 21845 18754 23 27. J� 1994 genksyms -rwxr-xr-x 1 root root 14184 31. Mai 2003 getty -rwxr-xr-x 1 root root 121032 16. Apr 2003 grub -rwxr-xr-x 1 root root 2944 16. Apr 2003 grub-floppy -rwxr-xr-x 1 root root 12110 16. Apr 2003 grub-install -rwxr-xr-x 1 root root...

..._ -Iinclude -include include/linux/autoconf.h -O2 -emit-llvm -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(missing_syscalls)" -D"KBUILD_MODNAME=KBUILD_STR(missing_syscalls)" make -f scripts/Makefile.build obj=scripts make -f scripts/Makefile.build obj=scripts/genksyms make -f scripts/Makefile.build obj=scripts/mod scripts/mod/mk_elfconfig x86_64 < scripts/mod/empty.o > scripts/mod/elfconfig.h Error: not ELF make[2]: *** [scripts/mod/elfconfig.h] Error 1 make[1]: *** [scripts/mod] Error 2 make: *** [scripts] Error 2 $cat scripts/Makefile.build hostprog...

...| 4 +-- > net/ipv6/udp.c | 4 +-- > net/lapb/lapb_iface.c | 4 +-- > net/llc/llc_input.c | 2 +- > scripts/checkpatch.pl | 8 ++--- > scripts/genksyms/keywords.c | 4 +-- > scripts/kernel-doc | 4 +-- > sound/sparc/amd7930.c | 6 ++-- > 165 files changed, 547 insertions(+), 547 deletions(-) -- Best Regards Masahiro Yamada

Hi all, I used the method described below to build client rpms with the source kit lustre-1.8.5.tar.gz. There was only one error reported during the make rpms, relating to lustre-iolit-1.2-root, but the rpms were built under /usr/src/packages/RPMS/x86_64. The rpms lustre-modules, lustre and lustre-tests were then installed smoothly without any complaints. But the subsequent "modprobe

...ace code KLIBCARCH ?= $(ARCH) +KLIBCARCHDIR ?= $(ARCH) # klibc definitions export KLIBCINC := usr/include @@ -326,7 +327,7 @@ export VERSION PATCHLEVEL SUBLEVEL KERNE export KLIBCARCH CONFIG_SHELL HOSTCC HOSTCFLAGS CROSS_COMPILE AS LD export CC CPP AR RANLIB NM STRIP OBJCOPY OBJDUMP MAKE AWK GENKSYMS export PERL UTS_MACHINE HOSTCXX HOSTCXXFLAGS LDFLAGS_MODULE CHECK -export CHECKFLAGS +export CHECKFLAGS KLIBCARCHDIR export CPPFLAGS NOSTDINC_FLAGS LINUXINCLUDE OBJCOPYFLAGS LDFLAGS export CFLAGS CFLAGS_KERNEL CFLAGS_MODULE diff -purN a/arch/s390/Makefile b/arch/s390/Makefile --- a/arch/s390...

On Tue, 2018-06-05 at 10:05 -0700, Nick Desaulniers wrote: > Functions marked extern inline do not emit an externally visible > function when the gnu89 C standard is used. Some KBUILD Makefiles > overwrite KBUILD_CFLAGS. This is an issue for GCC 5.1+ users as without > an explicit C standard specified, the default is gnu11. Since c99, the > semantics of extern inline have changed

On Tue, 2018-06-05 at 10:05 -0700, Nick Desaulniers wrote: > Functions marked extern inline do not emit an externally visible > function when the gnu89 C standard is used. Some KBUILD Makefiles > overwrite KBUILD_CFLAGS. This is an issue for GCC 5.1+ users as without > an explicit C standard specified, the default is gnu11. Since c99, the > semantics of extern inline have changed

I have updated the klibc patchset based on feedback received. In particular, the patchset has been reorganized so as not to break git-bisect. Additionally, this updates the patch base to 2.6.17-git12 (d38b69689c349f35502b92e20dafb30c62d49d63) and klibc 1.4.8; the main difference on the klibc side is removal of obsolete code. This is also available as a git tree at: