[Buildroot] ARM cross compiler path error "no such file or directory"

[Buildroot] ARM cross compiler path error "no such file or directory"

[Mark Jackson]

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 ??

[Buildroot] ARM cross compiler path error "no such file or directory"

[Thomas Petazzoni]

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.

Arnout? :-)

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

[Buildroot] ARM cross compiler path error "no such file or directory"

[Arnout Vandecappelle]

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".

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

[Buildroot] ARM cross compiler path error "no such file or directory"

[Thomas Petazzoni]

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

[Buildroot] [PATCH] toolchain-wrapper: fix breakage after host/usr removal

[Arnout Vandecappelle]

The toolchain wrapper, when called through PATH, strips the last three
levels of /proc/self/exe to find HOST_DIR. However, after the host/usr
removal, this should be just two levels.

The toolchain wrapper has different logic for when it is called with a
full path (i.e. $HOST_DIR/usr/bin/arm-linux-gcc) then when it is called
through the PATH (i.e. just arm-linux-gcc). The latter is never used
internally in Buildroot, that's why this wasn't discovered through
testing.

Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Cc: Mark Jackson <mpfj-list@newflow.co.uk>
---
Sorry for the breakage :-)

Note to self: add a test for calling the toolchain through PATH.

To fix an existing toolchain without rebuilding:
make host-gcc-final-rebuild
(or make host-toolchain-external-custom-rebuild if that's what you're
using).
---
 toolchain/toolchain-wrapper.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/toolchain/toolchain-wrapper.c b/toolchain/toolchain-wrapper.c
index 3a4455ff82..a73e6d6f94 100644
--- a/toolchain/toolchain-wrapper.c
+++ b/toolchain/toolchain-wrapper.c
@@ -192,7 +192,7 @@ int main(int argc, char **argv)
 		for (i = ret; i > 0; i--) {
 			if (absbasedir[i] == '/') {
 				absbasedir[i] = '\0';
-				if (++count == 3)
+				if (++count == 2)
 					break;
 			}
 		}
-- 
2.13.2

[Buildroot] [PATCH] toolchain-wrapper: fix breakage after host/usr removal

[Mark Jackson]

On 07/07/17 08:43, Arnout Vandecappelle (Essensium/Mind) wrote:
> The toolchain wrapper, when called through PATH, strips the last three
> levels of /proc/self/exe to find HOST_DIR. However, after the host/usr
> removal, this should be just two levels.
> 
> The toolchain wrapper has different logic for when it is called with a
> full path (i.e. $HOST_DIR/usr/bin/arm-linux-gcc) then when it is called
> through the PATH (i.e. just arm-linux-gcc). The latter is never used
> internally in Buildroot, that's why this wasn't discovered through
> testing.
> 
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Cc: Mark Jackson <mpfj-list@newflow.co.uk>

Tested-by: Mark Jackson <mpfj-list@newflow.co.uk>

Works fine now.  Cheers.

> ---
> Sorry for the breakage :-)
> 
> Note to self: add a test for calling the toolchain through PATH.
> 
> To fix an existing toolchain without rebuilding:
> make host-gcc-final-rebuild
> (or make host-toolchain-external-custom-rebuild if that's what you're
> using).
> ---
>   toolchain/toolchain-wrapper.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/toolchain/toolchain-wrapper.c b/toolchain/toolchain-wrapper.c
> index 3a4455ff82..a73e6d6f94 100644
> --- a/toolchain/toolchain-wrapper.c
> +++ b/toolchain/toolchain-wrapper.c
> @@ -192,7 +192,7 @@ int main(int argc, char **argv)
>   		for (i = ret; i > 0; i--) {
>   			if (absbasedir[i] == '/') {
>   				absbasedir[i] = '\0';
> -				if (++count == 3)
> +				if (++count == 2)
>   					break;
>   			}
>   		}
>

[Buildroot] [PATCH] toolchain-wrapper: fix breakage after host/usr removal

[Thomas Petazzoni]

Hello,

On Fri, 7 Jul 2017 09:43:30 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> The toolchain wrapper, when called through PATH, strips the last three
> levels of /proc/self/exe to find HOST_DIR. However, after the host/usr
> removal, this should be just two levels.
> 
> The toolchain wrapper has different logic for when it is called with a
> full path (i.e. $HOST_DIR/usr/bin/arm-linux-gcc) then when it is called
> through the PATH (i.e. just arm-linux-gcc). The latter is never used
> internally in Buildroot, that's why this wasn't discovered through
> testing.
> 
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Cc: Mark Jackson <mpfj-list@newflow.co.uk>
> ---
> Sorry for the breakage :-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] ARM cross compiler path error "no such file or directory"

[Marcus Hoffmann]

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

[Buildroot] ARM cross compiler path error "no such file or directory"

[Arnout Vandecappelle]

On 08-07-17 16:08, Marcus Hoffmann wrote:
> Hey Arnout,
> 
> On 06.07.2017 23:50, Arnout Vandecappelle wrote:
[snip]
>>  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"?

 That should indeed be the same.

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF