From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12656] New: bison fails to relocate with relocate-sdk.sh
Date: Tue, 17 Mar 2020 14:16:49 +0000 [thread overview]
Message-ID: <bug-12656-163@https.bugs.busybox.net/> (raw)
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.
next reply other threads:[~2020-03-17 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 14:16 bugzilla at busybox.net [this message]
2020-03-17 14:20 ` [Buildroot] [Bug 12656] bison fails to relocate with relocate-sdk.sh bugzilla at busybox.net
2020-05-18 6:27 ` bugzilla at busybox.net
2020-05-18 6:33 ` bugzilla at busybox.net
2020-05-19 19:25 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-12656-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox