Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] Linaro Toolchain for RPI and OABI Issues
@ 2019-11-12  7:11 rscr
  2019-11-12 19:15 ` Peter Seiderer
  0 siblings, 1 reply; 7+ messages in thread
From: rscr @ 2019-11-12  7:11 UTC (permalink / raw)
  To: buildroot

Hello, 

I am new on Buildroot and I am trying to build linux with buildroot for rpi
zero w.

I have successfully build a first version using the buildroot toolchain but
now I would like to use the rpi's one.
(https://github.com/raspberrypi/tools/tree/master/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64)

My host is running Ubuntu 16.04 on a 64-btis system.

The problem is that when building I get :

"External toolchain uses the unsuported OABI"

I am confused. I thought the rpi's toolchain is using the eabihf, is not? 

Find attached my _defconfig. 

Thanks in advance, 

Rafa cp4_defconfig.cp4_defconfig
<http://buildroot-busybox.2317881.n4.nabble.com/file/t2824/cp4_defconfig.cp4_defconfig>  







--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Buildroot] Linaro Toolchain for RPI and OABI Issues
  2019-11-12  7:11 [Buildroot] Linaro Toolchain for RPI and OABI Issues rscr
@ 2019-11-12 19:15 ` Peter Seiderer
  2019-11-13 13:07   ` rscr
  0 siblings, 1 reply; 7+ messages in thread
From: Peter Seiderer @ 2019-11-12 19:15 UTC (permalink / raw)
  To: buildroot

Hello rscr,

On Tue, 12 Nov 2019 01:11:39 -0600 (CST), rscr <rafacrespiramon@gmail.com> wrote:

> Hello,
>
> I am new on Buildroot and I am trying to build linux with buildroot for rpi
> zero w.
>
> I have successfully build a first version using the buildroot toolchain but
> now I would like to use the rpi's one.
> (https://github.com/raspberrypi/tools/tree/master/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64)
>
> My host is running Ubuntu 16.04 on a 64-btis system.
>
> The problem is that when building I get :
>
> "External toolchain uses the unsuported OABI"
>
> I am confused. I thought the rpi's toolchain is using the eabihf, is not?
>
> Find attached my _defconfig.
>
> Thanks in advance,
>
> Rafa cp4_defconfig.cp4_defconfig
> <http://buildroot-busybox.2317881.n4.nabble.com/file/t2824/cp4_defconfig.cp4_defconfig>

Could not reproduce your build problem using your given defconfig, did a fresh checkout of

	$ cd my_toolchain_patch
	$ git clone https://github.com/raspberrypi/tools.git

And adjusted

BR2_TOOLCHAIN_EXTERNAL_PATH="<my_toolchain_path>/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64"

Builds fine here (openSUSE Tumbleweed)

Regards,
Peter

>
>
>
>
>
>
>
> --
> Sent from: http://buildroot-busybox.2317881.n4.nabble.com/
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Buildroot] Linaro Toolchain for RPI and OABI Issues
  2019-11-12 19:15 ` Peter Seiderer
@ 2019-11-13 13:07   ` rscr
  2019-11-13 21:13     ` Peter Seiderer
  0 siblings, 1 reply; 7+ messages in thread
From: rscr @ 2019-11-13 13:07 UTC (permalink / raw)
  To: buildroot

Hi Peter, 

Keeps not working. 

I have changed to new recommended cross-compiler for x64
(arm-rpi-4.9.3-linux-gnueabihf) and I get the same error too.

Thanks



--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Buildroot] Linaro Toolchain for RPI and OABI Issues
  2019-11-13 13:07   ` rscr
@ 2019-11-13 21:13     ` Peter Seiderer
  2019-11-14 13:53       ` rscr
  0 siblings, 1 reply; 7+ messages in thread
From: Peter Seiderer @ 2019-11-13 21:13 UTC (permalink / raw)
  To: buildroot

Hello rscr,

On Wed, 13 Nov 2019 07:07:20 -0600 (CST), rscr <rafacrespiramon@gmail.com> wrote:

> Hi Peter,
>
> Keeps not working.
>
> I have changed to new recommended cross-compiler for x64
> (arm-rpi-4.9.3-linux-gnueabihf) and I get the same error too.

Are your sure buildroot uses your configured compiler?

Take a look at toolchain/helpers.mk and the check for OABI,
the check is (simpliefied):

	$ <yout_path_to_toolchain>/tools/arm-bcm2708/arm-bcm2708-linux-gnueabi/bin/arm-bcm2708-linux-gnueabi-gcc -v 2>&1 | grep ^Target | cut -f2 -d ' '
	arm-bcm2708-linux-gnueabi

	$ echo arm-bcm2708-linux-gnueabi | grep -E 'eabi(hf)?$$'
	arm-bcm2708-linux-gnueabi

Regards,
Peter

>
> Thanks
>
>
>
> --
> Sent from: http://buildroot-busybox.2317881.n4.nabble.com/
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Buildroot] Linaro Toolchain for RPI and OABI Issues
  2019-11-13 21:13     ` Peter Seiderer
@ 2019-11-14 13:53       ` rscr
  2019-11-14 14:15         ` Peter Seiderer
  0 siblings, 1 reply; 7+ messages in thread
From: rscr @ 2019-11-14 13:53 UTC (permalink / raw)
  To: buildroot

Hi Peter, 

I have checked if the toolchain was correctly installed and I have used the
checks that you suggested and I got this:

<http://buildroot-busybox.2317881.n4.nabble.com/file/t2824/Linaro_rpi_toolchain.jpg> 

The path that I am using on BR2_TOOLCHAIN_EXTERNAL_PATH is:

~/rcr/tools/toolchains/linaro/rpi/tools/arm-bcm2708/arm-rpi-4.9.3-linux-gnueabihf

Maybe I should have said this before, but I am using Ubuntu in dual boot
mode, along with Windows 10. Could this affect?

Kind Regards,
Rafa





--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Buildroot] Linaro Toolchain for RPI and OABI Issues
  2019-11-14 13:53       ` rscr
@ 2019-11-14 14:15         ` Peter Seiderer
  2019-11-15  7:27           ` rscr
  0 siblings, 1 reply; 7+ messages in thread
From: Peter Seiderer @ 2019-11-14 14:15 UTC (permalink / raw)
  To: buildroot

Hello rscr,

On Thu, 14 Nov 2019 07:53:13 -0600 (CST), rscr <rafacrespiramon@gmail.com> wrote:

> Hi Peter,
>
> I have checked if the toolchain was correctly installed and I have used the
> checks that you suggested and I got this:
>
> <http://buildroot-busybox.2317881.n4.nabble.com/file/t2824/Linaro_rpi_toolchain.jpg>

Looks good....

>
> The path that I am using on BR2_TOOLCHAIN_EXTERNAL_PATH is:
>
> ~/rcr/tools/toolchains/linaro/rpi/tools/arm-bcm2708/arm-rpi-4.9.3-linux-gnueabihf

Last try, use a absolute path here e.g. /home/<your login>/rcr/tools/toolchaines/linaro/rpi/tools/arm-bcm2708/arm-rpi-4.9.3-linux-gnueabihf

>
> Maybe I should have said this before, but I am using Ubuntu in dual boot
> mode, along with Windows 10. Could this affect?

Should not...

Regards,
Peter

>
> Kind Regards,
> Rafa
>
>
>
>
>
> --
> Sent from: http://buildroot-busybox.2317881.n4.nabble.com/
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Buildroot] Linaro Toolchain for RPI and OABI Issues
  2019-11-14 14:15         ` Peter Seiderer
@ 2019-11-15  7:27           ` rscr
  0 siblings, 0 replies; 7+ messages in thread
From: rscr @ 2019-11-15  7:27 UTC (permalink / raw)
  To: buildroot

Hi Peter, 

With BR2_TOOLCHAIN_EXTERNAL_PATH  =  /home/<your
login>/rcr/tools/toolchaines/linaro/rpi/tools/arm-bcm2708/arm-rpi-4.9.3-linux-gnueabihf
worked!

Thanks a lot, 

Rafa



--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2019-11-15  7:27 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-11-12  7:11 [Buildroot] Linaro Toolchain for RPI and OABI Issues rscr
2019-11-12 19:15 ` Peter Seiderer
2019-11-13 13:07   ` rscr
2019-11-13 21:13     ` Peter Seiderer
2019-11-14 13:53       ` rscr
2019-11-14 14:15         ` Peter Seiderer
2019-11-15  7:27           ` rscr

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox