From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11031] New: ld-elf2flt: host/bin/ld.real': execvp: No such file or directory
Date: Wed, 23 May 2018 10:14:17 +0000 [thread overview]
Message-ID: <bug-11031-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11031
Bug ID: 11031
Summary: ld-elf2flt: host/bin/ld.real': execvp: No such file or
directory
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: critical
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: christophe.priouzeau at st.com
CC: buildroot at uclibc.org
Target Milestone: ---
With the rc of 2018.05 preparation, it's not possible to generate uclibc with a
stm32 build.
During the installation of uclibc, the call to elf2flt crash:
CC utils/getconf
ld.real (ld-elf2flt): error trying to exec
'/mnt/internal_storage/stm32f7/buildroot_to_test/output/host/bin/ld.real':
execvp: No such file or directory
collect2: error: ld returned 255 exit status
Setup:
VERSION of buildroot: 2018.05-rc2
PC with Ubuntu 16.04
How to reproduce:
git clone git://git.buildroot.net/buildroot
cd buildroot
git checkout -b work 2018.05-rc2
make stm32f469_disco_defconfig
make
Trace of compilation are available on attached file.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-05-23 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 10:14 bugzilla at busybox.net [this message]
2018-05-23 17:49 ` [Buildroot] [Bug 11031] ld-elf2flt: host/bin/ld.real': execvp: No such file or directory bugzilla at busybox.net
2018-05-25 20:51 ` bugzilla at busybox.net
2018-05-28 20:58 ` bugzilla at busybox.net
2018-05-29 7:09 ` 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-11031-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.