From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5570] New: Cannot compile software on the target machine
Date: Mon, 24 Sep 2012 11:05:46 +0000 (UTC) [thread overview]
Message-ID: <bug-5570-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=5570
Host: x86_64 Arch Linux box
Target: arm (littel endian) arm1176jzf-s (BCM2708)
Summary: Cannot compile software on the target machine
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: mari.hahn at uni-muenster.de
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Version: buildroot-20120922.tar.bz2
While compiling simple hello world programs on the target machine does work,
compiling complex software doesn't.
I get error messages like this one:
libtool: link: warning: library `/usr/lib/libintl.la' was moved.
grep:
/home/maribu/buildroot/buildroot/output/host/usr/arm-unknown-linux-uclibcgnueabi/sysroot/usr/lib//libiconv.la:
No such file or directory
sed:
/home/maribu/buildroot/buildroot/output/host/usr/arm-unknown-linux-uclibcgnueabi/sysroot/usr/lib//libiconv.la:
No such file or directory
libtool: link:
`/home/maribu/buildroot/buildroot/output/host/usr/arm-unknown-linux-uclibcgnueabi/sysroot/usr/lib//libiconv.la'
is not a valid libtool archive
the libtool archive "libintl.la" is present at /usr/lib, but libtool is
searching for it in
"/home/maribu/buildroot/buildroot/output/host/usr/arm-unknown-linux-uclibcgnueabi/sysroot/usr/lib/"
which was the correct path on the cross compiling host, but not on the target.
I tried to export LD_LIBARY_PATH=/usr/lib which does work as root, bus for some
reason is completely ignored (without any feedback) as normal user.
I think this is a bug, because in my humble opinion there should be no
reference to host specific paths within the resulting image.
I would be very happy if someone would suggest a quick workaround so I can
start compiling again.
Regards,
Maribu
--
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-09-24 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 11:05 bugzilla at busybox.net [this message]
2012-09-24 14:10 ` [Buildroot] [Bug 5570] Cannot compile software on the target machine bugzilla at busybox.net
2012-09-24 14:27 ` bugzilla at busybox.net
2012-09-24 17:09 ` bugzilla at busybox.net
2012-09-24 20:13 ` bugzilla at busybox.net
2013-11-28 17: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-5570-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.