From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 4399] New: Unable to use Ubuntu 11.10 arm cross compiler
Date: Sat, 29 Oct 2011 15:30:00 +0000 (UTC) [thread overview]
Message-ID: <bug-4399-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=4399
Summary: Unable to use Ubuntu 11.10 arm cross compiler
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: fenixk19 at mail.ru
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Attempt to use ubuntu arm cross-compiler (package gcc-4.6-arm-linux-gnueabi) as
an external toolchain fails with the following message:
Checking external toolchain settings
Incorrect selection of the C library
make: ***
[/home/fenixk19/Development/samsung/OS/buildroot/output/stamps/ext-toolchain-checked]
?????? 255
Thats because there is a string in ext-tool.mk:
SYSROOT_DIR=`readlink -f $$(LANG=C $(TOOLCHAIN_EXTERNAL_CC)
-print-file-name=libc.a) |sed -r -e 's:usr/lib/libc\.a::;'` ;
But "arm-linux-gnueabi-gcc -print-file-name=libc.a" returns
"/usr/lib/gcc/arm-linux-gnueabi/4.6.1/../../../../arm-linux-gnueabi/lib/../lib/libc.a"
So sed works with wrong pattern here. This should be 's:lib/libc\.a::;' for
Ubuntu.
--
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:[~2011-10-29 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 15:30 bugzilla at busybox.net [this message]
2011-10-29 15:36 ` [Buildroot] [Bug 4399] Unable to use Ubuntu 11.10 arm cross compiler bugzilla at busybox.net
2011-10-30 20:27 ` 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-4399-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