[lfs-support] expr core dump

Alexey Orishko alexey.orishko at gmail.com
Sun Jun 21 11:09:20 PDT 2015


On Sun, Jun 21, 2015 at 7:45 PM, Bruce Dubbs <bruce.dubbs at gmail.com> wrote:
>
> Are you trying it in a partial chroot or a complete one?  It's really a
> pretty simple program.
>
> $ ldd /usr/bin/expr
>         linux-vdso.so.1 (0x00007ffdd7897000)
>         libgmp.so.10 => /usr/lib/libgmp.so.10 (0x00007fede2217000)
>         libc.so.6 => /lib/libc.so.6 (0x00007fede1e75000)
>         /lib64/ld-linux-x86-64.so.2 (0x00007fede248c000)
>

I have a complete BLFS-7.7 with some minor changes (terminal only
version). I've noticed this problem compiling modified kernel:

kernel/sys.c:1118:28: error: expected expression before ‘>>’ token
   v = ((LINUX_VERSION_CODE >> 8) & 0xff) + 40;
                            ^
scripts/Makefile.build:257: recipe for target 'kernel/sys.o' failed
make[1]: *** [kernel/sys.o] Error 1
Makefile:937: recipe for target 'kernel' failed
make: *** [kernel] Error 2

I can see LINUX_VERSION_CODE is blank in include/generated/uapi/linux/version.h

cat include/generated/uapi/linux/version.h
#define LINUX_VERSION_CODE
#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))

Colleague of mine pointed to expr as a source of the problem during
kernel compile...

Actually, after double checking, the same problem exists on the live
system (kernel 3.18.11 64bit):
# expr 7 \* 9
Illegal instruction

I wonder if we use expr from /tools during initial kernel build in LFS
(coz that part works fine) and after re-entering chroot during BLFS
build or while using real system I'm using a different version of
expr...

Regards,
Alexey


More information about the lfs-support mailing list