[Buildroot] Building only toolchain

[Buildroot] Building only toolchain

[Teemu Keskinarkaus]

Hi,

 

Is it possible to build only toolchain in buildroot? I tried to search
the makefiles, but I couldn't find a target that would do it.  It seems
that there are some absolute paths stored in buildroot toolchain
binaries(at least ccache has) so I can't just copy them to another
system. Or can the toolchain be built somehow that it doesn't store any
local information there?

 

I don't want to build whole system, but just applications so only
toolchain is needed and not the whole buildroot. I also like to use the
same toolchain that was used in buildroot to prevent any problems that
might come from using different toolchain.

 

Teemu Keskinarkaus

 

Software System Engineer

CC Systems Oy

Finlaysoninkuja 21, 33210 Tampere, Finland 

Mobile +358 400 330 047

Switchboard +358 207 699 190

Fax +358 207 699 199

www.cc-systems.com <http://www.cc-systems.com/> 

 

CC Systems

- advanced machine controls

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090529/74a1d35c/attachment.htm>

[Buildroot] Building only toolchain

[Bjørn Forsman]

2009/5/29 Teemu Keskinarkaus <Teemu.Keskinarkaus@cc-systems.com>

>  Hi,
>
>
>
> Is it possible to build only toolchain in buildroot? I tried to search the
> makefiles, but I couldn?t find a target that would do it.  It seems that
> there are some
>
<snipped>
I know this is not directly what you asked for, but do you know about the
crosstool-ng project? It builds both glibc/uClibc based toolchains for
several architectures. I successfully built an ARM toolchain with it a
couple of months ago. Project website:
http://ymorin.is-a-geek.org/dokuwiki/projects/crosstool

> I don?t want to build whole system, but just applications so only toolchain
> is needed and not the whole buildroot. I also like to use the same toolchain
> that was used in buildroot to prevent any problems that might come from
> using different toolchain.
>
I have not tested it myself, but I guess it should be ok to setup Buildroot
to use a crosstool-ng generated external toolchain.
Regards,
Bj?rn Forsman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090529/1879e6b6/attachment.htm>

[Buildroot] Building only toolchain

[Thomas Petazzoni]

Le Fri, 29 May 2009 09:21:02 +0200,
Bj?rn Forsman <bjorn.forsman@gmail.com> a ?crit :

> I have not tested it myself, but I guess it should be ok to setup
> Buildroot to use a crosstool-ng generated external toolchain.

It is ok, through the ? External binary toolchain ? option of the
Toolchain menu.

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

[Buildroot] Building only toolchain

[Peter Korsgaard]

>>>>> "Teemu" == Teemu Keskinarkaus <Teemu.Keskinarkaus@cc-systems.com> writes:

 Teemu> Hi,

 Teemu> Is it possible to build only toolchain in buildroot? I tried
 Teemu> to search the makefiles, but I couldn?t find a target that
 Teemu> would do it.

Sure, simply don't select and packages and no file systems, then it
will only build the toolchain.

 Teemu> It seems that there are some absolute paths stored in
 Teemu> buildroot toolchain binaries(at least ccache has) so I can?t
 Teemu> just copy them to another system. Or can the toolchain be
 Teemu> built somehow that it doesn?t store any local information
 Teemu> there?

Yes, the BR output is in general not relocatable.

 Teemu> I don?t want to build whole system, but just applications so
 Teemu> only toolchain is needed and not the whole buildroot. I also
 Teemu> like to use the same toolchain that was used in buildroot to
 Teemu> prevent any problems that might come from using different
 Teemu> toolchain.

No problem, as long as you don't move the toolchain around. We often
build pure toolchains with STAGING_DIR set to something like
/opt/cross/${DATE}, which can then simply be added to the path and
used.

-- 
Bye, Peter Korsgaard

[Buildroot] Building only toolchain

[Teemu Keskinarkaus]

> -----Original Message-----
> From: Peter Korsgaard [mailto:jacmet at gmail.com] On Behalf Of Peter
> No problem, as long as you don't move the toolchain around. We often
> build pure toolchains with STAGING_DIR set to something like
> /opt/cross/${DATE}, which can then simply be added to the path and
> used.
That helped. I set the staging dir to point somewhere else. Then I
needed to disable ccache since it stored the buildroot directory
somewhere and if I removed the buildroot the compiler wouldn't work. But
now, with ccache disabled, it works just fine even if the buildroot is
removed. 

Thanks!

-Teemu

[Buildroot] Building only toolchain

[Peter Korsgaard]

>>>>> "Teemu" == Teemu Keskinarkaus <Teemu.Keskinarkaus@cc-systems.com> writes:

 >> -----Original Message-----
 >> From: Peter Korsgaard [mailto:jacmet at gmail.com] On Behalf Of Peter
 >> No problem, as long as you don't move the toolchain around. We often
 >> build pure toolchains with STAGING_DIR set to something like
 >> /opt/cross/${DATE}, which can then simply be added to the path and
 >> used.
 Teemu> That helped. I set the staging dir to point somewhere else. Then I
 Teemu> needed to disable ccache since it stored the buildroot directory
 Teemu> somewhere and if I removed the buildroot the compiler wouldn't work. But
 Teemu> now, with ccache disabled, it works just fine even if the buildroot is
 Teemu> removed. 

Yes, I think we should get rid of the ccache patch to put the cache
dir in buildroot.

Good to hear that it otherwise works.

-- 
Bye, Peter Korsgaard

[Buildroot] Building only toolchain

[Bernhard Reutner-Fischer]

On Fri, May 29, 2009 at 07:25:19AM +0200, Teemu Keskinarkaus wrote:
>Hi,
>
> 
>
>Is it possible to build only toolchain in buildroot? I tried to search

yes. IIRC 'make cross_compiler'

>the makefiles, but I couldn't find a target that would do it.  It seems
>that there are some absolute paths stored in buildroot toolchain

You should always use SYSROOT-enabled compilers thus building a compiler
that you can trivially relocate.

>binaries(at least ccache has) so I can't just copy them to another
>system. Or can the toolchain be built somehow that it doesn't store any
>local information there?

[Buildroot] Building only toolchain

[Teemu Keskinarkaus]

> From: Bernhard Reutner-Fischer [mailto:rep.dot.nop at gmail.com]
> >Is it possible to build only toolchain in buildroot? I tried to
search
> yes. IIRC 'make cross_compiler'
Yes, that seems to be correct. 

> >the makefiles, but I couldn't find a target that would do it.  It
seems
> >that there are some absolute paths stored in buildroot toolchain
> 
> You should always use SYSROOT-enabled compilers thus building a
compiler
> that you can trivially relocate.
SYSROOT is actually enabled, but the problem was ccache that stores
buildroot directory somewhere itself. This was discussed in another mail
regarding this same thing.

But this problem is solved now and I can compile cross compiler that
works with out any references to actual buildroot anymore.

Thanks.

-Teemu