From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] ARM cross compiler path error "no such file or directory"
Date: Fri, 7 Jul 2017 09:24:06 +0200 [thread overview]
Message-ID: <20170707092406.722b80f4@windsurf.lan> (raw)
In-Reply-To: <da907d83-16e4-4b89-6d4b-db3d686a2a85@mind.be>
Hello,
On Thu, 6 Jul 2017 23:50:39 +0200, Arnout Vandecappelle wrote:
> > On Thu, 6 Jul 2017 15:34:27 +0100, Mark Jackson wrote:
> >
> >> I can successfully compile "beaglebone_defconfig".
> >>
> >> $ make clean
> >> $ make beaglebone_defconfig
> >> $ make
> >>
> >> And in output/host/usr/bin, I can find all the "arm-linux-xyz" cross compiler tools (gcc, strings, strip, etc).
> >>
> >> But when I try to use these to compile my own code, I get an error as follows:-
> >>
> >> $ which arm-linux-gcc
> >> /home/mpfj/buildroot/output/host/usr/bin/arm-linux-gcc
> >> $ arm-linux-gcc
> >> /home/mpfj/buildroot/output/usr/bin/arm-linux-gcc.br_real: No such file or directory
> >>
> >> Quite correctly, "output/usr/bin" doesn't exist ... the files are in "output/host/usr/bin"
> >>
> >> arm-linux-gcc is just a symlink to toolchain-wrapper, so toolchain-wrapper seems to be pointing to the wrong directory!!
> >>
> >> I'm sure was working yesterday, but I did a "git pull" this morning, so it may be something quite recent ??
> >
> > We pushed some changes over the last few days that moved everything in
> > $(HOST_DIR)/usr up into $(HOST_DIR), so it is possible that there are
> > some regressions.
>
> You need to rebuild the toolchain (actually the toolchain wrapper) after this
> change. And probably other things need to be rebuilt as well. To be safe, do a
> "make clean; make".
Re-read the original message from Mark: he starts by saying that he has
done "make clean; make beaglebone_defconfig; make".
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-07 7:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 14:34 [Buildroot] ARM cross compiler path error "no such file or directory" Mark Jackson
2017-07-06 15:35 ` Thomas Petazzoni
2017-07-06 21:50 ` Arnout Vandecappelle
2017-07-07 7:24 ` Thomas Petazzoni [this message]
2017-07-07 7:43 ` [Buildroot] [PATCH] toolchain-wrapper: fix breakage after host/usr removal Arnout Vandecappelle
2017-07-07 11:12 ` Mark Jackson
2017-07-07 11:58 ` Thomas Petazzoni
2017-07-08 14:08 ` [Buildroot] ARM cross compiler path error "no such file or directory" Marcus Hoffmann
2017-07-08 15:20 ` Arnout Vandecappelle
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=20170707092406.722b80f4@windsurf.lan \
--to=thomas.petazzoni@free-electrons.com \
--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