[Buildroot] toolchain into the root disk

[Buildroot] toolchain into the root disk

[Max]

Hi all,

Is there any way to setup builroot to insert a toolchain into the root disk?

Thank you,
MaX

P.s
I am using builroot for powerpc and it works really fine. Thaks to all the
developpers =)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110304/71055938/attachment.html>

[Buildroot] toolchain into the root disk

[Thomas Petazzoni]

On Fri, 4 Mar 2011 16:47:42 +0000
Max <themaxmail@gmail.com> wrote:

> Is there any way to setup builroot to insert a toolchain into the
> root disk?

See the BR2_PACKAGE_GCC_TARGET option, which allows to enable toolchain
in the target.

However, remember that Buildroot is a *cross-compilation* build system:
its purpose is to cross-compile libraries and programs for the target.
Therefore, the target toolchain (which allows to do native compilation
on the target) is not that widely used, and therefore not that widely
tested.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] toolchain into the root disk

[Max]

Hi Thomas,

the BR2_PACKAGE_GCC_TARGET seams to me to work only with the internal
toolchain.

I'm creating a root disk for a powerpc64 architecture. As build root does
not support powerpc64, I'm
using and external toolchain. With few workarounds evething works fine.

When I use BR2_PACKAGE_GCC_TARGET=y the tool tries to download gcc but the
version is not
define so it tries to get the file gcc-.tar.bz2.

Can you please tell me where in the tool the gcc version is set? I was not
able to spot the location.

Thanks,
Massimiliano


On Mon, Mar 7, 2011 at 1:33 PM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> On Fri, 4 Mar 2011 16:47:42 +0000
> Max <themaxmail@gmail.com> wrote:
>
> > Is there any way to setup builroot to insert a toolchain into the
> > root disk?
>
> See the BR2_PACKAGE_GCC_TARGET option, which allows to enable toolchain
> in the target.
>
> However, remember that Buildroot is a *cross-compilation* build system:
> its purpose is to cross-compile libraries and programs for the target.
> Therefore, the target toolchain (which allows to do native compilation
> on the target) is not that widely used, and therefore not that widely
> tested.
>
> Regards,
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110307/66a7eca0/attachment.html>

[Buildroot] toolchain into the root disk

[Thomas Petazzoni]

Hello,

On Mon, 7 Mar 2011 16:54:23 +0000
Max <themaxmail@gmail.com> wrote:

> the BR2_PACKAGE_GCC_TARGET seams to me to work only with the internal
> toolchain.

Yes. Nobody has done the effort on getting BR2_PACKAGE_GCC_TARGET to
work with external toolchain as of today. As said previously, Buildroot
is a cross-compiling environment, so the need of a toolchain on the
target is not very common.

> I'm creating a root disk for a powerpc64 architecture. As build root does
> not support powerpc64, I'm
> using and external toolchain. With few workarounds evething works fine.

Just curious, which toolchain have you used ?

> When I use BR2_PACKAGE_GCC_TARGET=y the tool tries to download gcc but the
> version is not
> define so it tries to get the file gcc-.tar.bz2.

Yes, correct.

> Can you please tell me where in the tool the gcc version is set? I was not
> able to spot the location.

It isn't set in the external toolchain case, that's the problem. I now
Gustavo Zacarias has planned to rework the gcc handling, and it should
probably fix this problem.

In the mean time, you can force the GCC version by modifying the code,
but you'll very likely have issues when building gcc for the target.

Do you really need a native toolchain on the target ? What do you want
to build on the target ?

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] toolchain into the root disk

[Max]

>Just curious, which toolchain have you used ?

I built a x86-powerpc64 cross compiler based on gcc-4.5.2 and glibc-2.12.2

>In the mean time, you can force the GCC version by modifying the code,
>but you'll very likely have issues when building gcc for the target.

I will take the risk =)

>Do you really need a native toolchain on the target ? What do you want
>to build on the target ?

I prefer to have the toolchain also on the target for quick recompilation
during
debugging phase =P

__
Massimiliano

On Mon, Mar 7, 2011 at 5:21 PM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Hello,
>
> On Mon, 7 Mar 2011 16:54:23 +0000
> Max <themaxmail@gmail.com> wrote:
>
> > the BR2_PACKAGE_GCC_TARGET seams to me to work only with the internal
> > toolchain.
>
> Yes. Nobody has done the effort on getting BR2_PACKAGE_GCC_TARGET to
> work with external toolchain as of today. As said previously, Buildroot
> is a cross-compiling environment, so the need of a toolchain on the
> target is not very common.
>
> > I'm creating a root disk for a powerpc64 architecture. As build root does
> > not support powerpc64, I'm
> > using and external toolchain. With few workarounds evething works fine.
>
> Just curious, which toolchain have you used ?
>
> > When I use BR2_PACKAGE_GCC_TARGET=y the tool tries to download gcc but
> the
> > version is not
> > define so it tries to get the file gcc-.tar.bz2.
>
> Yes, correct.
>
> > Can you please tell me where in the tool the gcc version is set? I was
> not
> > able to spot the location.
>
> It isn't set in the external toolchain case, that's the problem. I now
> Gustavo Zacarias has planned to rework the gcc handling, and it should
> probably fix this problem.
>
> In the mean time, you can force the GCC version by modifying the code,
> but you'll very likely have issues when building gcc for the target.
>
> Do you really need a native toolchain on the target ? What do you want
> to build on the target ?
>
> Regards,
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110307/fd0b1fa9/attachment.html>

[Buildroot] toolchain into the root disk

[Thomas Petazzoni]

On Mon, 7 Mar 2011 17:46:28 +0000
Max <themaxmail@gmail.com> wrote:

> >Do you really need a native toolchain on the target ? What do you want
> >to build on the target ?
> 
> I prefer to have the toolchain also on the target for quick recompilation
> during debugging phase =P

I don't see why having the toolchain on the target makes it any
quicker. Just cross-compile your application, make your root filesystem
mounted over NFS, and use cross-debugging. There are zero extra steps
when compared to native building your application.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com