[Buildroot] [Bug 12656] New: bison fails to relocate with relocate-sdk.sh
bugzilla at busybox.net
bugzilla at busybox.net
Tue Mar 17 14:16:49 UTC 2020
https://bugs.busybox.net/show_bug.cgi?id=12656
Bug ID: 12656
Summary: bison fails to relocate with relocate-sdk.sh
Product: buildroot
Version: 2019.11
Hardware: All
OS: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: marcelo.jimenez at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
Hi,
I am having a problem while compiling the linux kernel with a toolchain
generated by buildroot. The git tag for the toolchain build is "2019.11":
PIG_KERNEL_MAKE=/home/user/prog/scripts/pig-kmake.sh --ccache
/home/user/prog/tmp/arm /home/user/prog/tmp/linux ARCH=arm
CROSS_COMPILE=arm-buildroot-linux-gnueabi-
PWD=/home/user/prog
kernel defconfig ........................................................
[Fail(B]
/home/user/prog/scripts/pig-kmake.sh --ccache /home/user/prog/tmp/arm
/home/user/prog/tmp/linux ARCH=arm CROSS_COMPILE=arm-buildroot-linux-gnueabi-
cpti-arietta_defconfig
make[1]: Entering directory '/home/user/prog/tmp/arm'
GEN ./Makefile
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
YACC scripts/kconfig/zconf.tab.c
LEX scripts/kconfig/zconf.lex.c
bison: /home/user/buildroot/output/host/share/bison/m4sugar/m4sugar.m4: cannot
open: No such file or directory
make[2]: *** [scripts/Makefile.lib:196: scripts/kconfig/zconf.tab.c] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [/home/user/prog/linux/Makefile:534: cpti-arietta_defconfig] Error
2
make[1]: Leaving directory '/home/user/prog/tmp/arm'
make: *** [Makefile:146: sub-make] Error 2
The problem seems to be the same as the one reported here:
https://github.com/bootlin/toolchains-builder/issues/17
The toolchain has been generated in one machine and is beeing used in another
different machine. Somehow bison still keeps its absolute path dependency.
Best regards,
Marcelo.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the buildroot
mailing list