From: Piotr Grudzinski <piotr@powersmiths.com>
To: crossgcc@sourceware.org
Subject: ld.real: execvp: No such file or directory
Date: Thu, 05 Jan 2012 21:29:00 -0000 [thread overview]
Message-ID: <CACGRwV35y7DvvpHy+vgE_j-de3NPdqUw6KcFV-=fOo2AE-c0BQ@mail.gmail.com> (raw)
Hello,
I'm having problem building crosstool for ARM no-mmu system (see below):
[INFO ] =================================================================
[INFO ] Installing C library
[EXTRA] Copying sources to build dir
[EXTRA] Applying configuration
[EXTRA] Building C library
[ERROR] make[1]: *** [lib/ld-uClibc.so] Error 1
[ERROR]
[ERROR] >>
[ERROR] >> Error happened in: main[scripts/crosstool-NG.sh]
[ERROR] >>
[ERROR] >> For more info on this error, look at the file: 'build.log'
And from build.log file:
[ALL ] LD ld-uClibc-0.9.30.2.so
[ALL ] ld (ld-elf2flt): error trying to exec
'/home/piotr/x-tools/arm-unknown-linux-uclibc/bin/ld.real': execvp: No
such file or directory
[ALL ] collect2: ld returned 255 exit status
[ERROR] make[1]: *** [lib/ld-uClibc.so] Error 1
[ALL ] make[1]: *** Waiting for unfinished jobs....
[ALL ] make[1]: Leaving directory
`/home/piotr/toolchain-build/.build/arm-unknown-linux-uclibc/build/build-libc'
The ld.real program is in:
/home/piotr/x-tools/arm-unknown-linux-uclibc/arm-unknown-linux-uclibc/bin
directory.
I my /home/piotr/x-tools/arm-unknown-linux-uclibc/bin directory there
is a arm-unknown-linux-uclibc-ld.real
file.
It looks like the build system is looking for ld.real in a wrong
directory or arm-unknown-linux-uclibc-ld.real should be used instead.
Any suggestions how/where to fix this problem?
Best Regards,
Piotr
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2012-01-05 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 21:29 Piotr Grudzinski [this message]
2012-01-07 13:38 ` Piotr Grudzinski
2012-01-16 17:50 ` Yann E. MORIN
2012-01-17 3:34 ` Piotr Grudzinski
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='CACGRwV35y7DvvpHy+vgE_j-de3NPdqUw6KcFV-=fOo2AE-c0BQ@mail.gmail.com' \
--to=piotr@powersmiths.com \
--cc=crossgcc@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).