[Buildroot] ARM cross compiler path error "no such file or directory"
Marcus Hoffmann
m.hoffmann at cartelsol.com
Sat Jul 8 14:08:54 UTC 2017
Hey Arnout,
On 06.07.2017 23:50, Arnout Vandecappelle wrote:
>
>
> On 06-07-17 17:35, Thomas Petazzoni wrote:
>> Hello,
>>
>> 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".
Now I wonder, is there any difference to doing "make clean all"?
>
> Regards,
> Arnout
Best wishes,
Marcus
More information about the buildroot
mailing list