From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8456] New: Building host-pkgconf on Fedora 23 fails due to incorrect build dependencies
Date: Tue, 10 Nov 2015 13:36:04 +0000 (UTC) [thread overview]
Message-ID: <bug-8456-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8456
Summary: Building host-pkgconf on Fedora 23 fails due to
incorrect build dependencies
Product: buildroot
Version: 2015.08
Platform: PC
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: ian_ormshaw at waters.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
When building on Fedora 23 with a previously working configuration I receive
the following error:
ls: symbol lookup error: ls: undefined symbol: cap_get_file
configure: error: working directory cannot be determined
This is caused by the by the following lines in the configure script.
1127 ac_pwd=`pwd` && test -n "$ac_pwd" &&
1128 ac_ls_di=`ls -di .` &&
1129 ac_pwd_ls_di=`cd "$ac_pwd" && ls -di .` ||
1130 as_fn_error $? "working directory cannot be determined"
1131 test "X$ac_ls_di" = "X$ac_pwd_ls_di" ||
1132 as_fn_error $? "pwd does not report name of working directory"
This line calls /bin/ls as there is no host ls provided by buildroot, but ls
uses LD_LIBRARY_PATH as set by buildroot to locate the shared libraries it
requires and therefore opens:
${buildpath}/host/usr/lib/libcap.so.2
The same effect can be achieved by typing:
LD_LIBRARY_PATH=${buildpath}/host/usr/lib ls -dl .
Temperately modifying the configure script to be:
1127 LD_LIBRARY_PATH= ac_pwd=`pwd` && test -n "$ac_pwd" &&
1128 ac_ls_di=`ls -di .` &&
1129 ac_pwd_ls_di=`cd "$ac_pwd" && ls -di .` ||
1130 as_fn_error $? "working directory cannot be determined"
1131 test "X$ac_ls_di" = "X$ac_pwd_ls_di" ||
1132 as_fn_error $? "pwd does not report name of working directory"
Allows the build to continue. But the same problem is encountered in building
other host packages.
But it would appear to be a dependency issue. I think the build order should
be that
host-coreutils and host-libcap needs to be build before any other host packages
that use ls (or any other commands used in configure scripts).
--
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:[~2015-11-10 13:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 13:36 bugzilla at busybox.net [this message]
2015-11-10 17:50 ` [Buildroot] [Bug 8456] Building host-pkgconf on Fedora 23 fails due to incorrect build dependencies bugzilla at busybox.net
2015-11-11 10:27 ` bugzilla at busybox.net
2015-11-11 15:26 ` bugzilla at busybox.net
2015-11-12 22:44 ` bugzilla at busybox.net
2015-11-18 12:30 ` bugzilla at busybox.net
2015-11-18 23:06 ` 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-8456-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