From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 4868] New: Buildroot compile failure for toolchain/gdb-7.4/intl/relocatable.c
Date: Tue, 6 Mar 2012 19:02:07 +0000 (UTC) [thread overview]
Message-ID: <bug-4868-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=4868
Summary: Buildroot compile failure for
toolchain/gdb-7.4/intl/relocatable.c
Product: buildroot
Version: 2012.02
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: ps.report at gmx.net
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 4082
--> https://bugs.busybox.net/attachment.cgi?id=4082
buildroot config file
Attached a fix/patch for the following compile failure with buildroot and
gdb-7.4 (.config file attached):
make[3]: Entering directory `/tmp//build-001/build/gdb-7.4-target/libiberty'
make[4]: Entering directory
`/tmp//build-001/build/gdb-7.4-target/libiberty/testsuite'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/tmp//build-001/build/gdb-7.4-target/libiberty/testsuite'
make[3]: Leaving directory `/tmp//build-001/build/gdb-7.4-target/libiberty'
make[3]: Entering directory `/tmp//build-001/build/gdb-7.4-target/intl'
rm -f stamp-h1
/bin/sh ./config.status config.h
config.status: creating config.h
config.status: config.h is unchanged
test -f config.h || (rm -f stamp-h1 && /usr/bin/make stamp-h1)
/tmp//build-001/host/usr/bin/x86_64-unknown-linux-uclibc-gcc -c -pipe -Os -g2
-fPIC -DPIC -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-Wno-error -DHAVE_CONFIG_H -DINSTALLDIR="\"/usr/lib\"" -I.
-I/tmp//build-001/toolchain/gdb-7.4/intl
/tmp//build-001/toolchain/gdb-7.4/intl/relocatable.c
/tmp//build-001/toolchain/gdb-7.4/intl/relocatable.c: In function
?libintl_relocate?:
/tmp//build-001/toolchain/gdb-7.4/intl/relocatable.c:392:40: error:
?INSTALLPREFIX? undeclared (first use in this function)
/tmp//build-001/toolchain/gdb-7.4/intl/relocatable.c:392:40: note: each
undeclared identifier is reported only once for each function it appears in
make[3]: *** [relocatable.o] Error 1
make[3]: Leaving directory `/tmp//build-001/build/gdb-7.4-target/intl'
make[2]: *** [all-intl] Error 2
make[2]: Leaving directory `/tmp//build-001/build/gdb-7.4-target'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp//build-001/build/gdb-7.4-target'
make: *** [/tmp//build-001/build/gdb-7.4-target/gdb/gdb] Error 2
make: Leaving directory `/tmp//buildroot'
I think the relevant config options to hit this bug are:
BR2_PACKAGE_GDB=y
BR2_PACKAGE_GDB_SERVER=y
BR2_GDB_VERSION_7_4=y
BR2_GDB_VERSION="7.4"
BR2_ENABLE_LOCALE=y
Analysis: the Makefile for the gdb-7.4 embedded (lib-)intl fails to set a
define for 'INSTALLPREFIX'.
Fix: see attached buildroot patch
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2012-03-06 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 19:02 bugzilla at busybox.net [this message]
2012-03-06 19:04 ` [Buildroot] [Bug 4868] Buildroot compile failure for toolchain/gdb-7.4/intl/relocatable.c bugzilla at busybox.net
2012-03-06 20:03 ` bugzilla at busybox.net
2013-05-26 13:52 ` 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-4868-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.