* [Buildroot] How to deploy Buildroot's crosscompile toolchain???
@ 2014-10-05 6:32 Tal Lubko
2014-10-05 6:38 ` Waldemar Brodkorb
2014-10-05 9:50 ` Peter Kuemmel
0 siblings, 2 replies; 6+ messages in thread
From: Tal Lubko @ 2014-10-05 6:32 UTC (permalink / raw)
To: buildroot
Hi
I've wanted to ask what is the right way to build and deploy Buildroot'stoolchain to other machines?
These machines don't have Buildroot to build the toolchain.
Currently (being ignorant about the right way to do it), after building the toolcahin, I'm just making a tar of output/host and copy it to other machine. There I'm untarring it to some directory and starting to cross compile...
Things seemed to be working when I've worked with an External toolchain (SourceryCodeBench). However when I've switched to Buildroot'stoolchain, I got a message about missing libmpc.so.3. Then I've started to wonder what is the right way to build and deploy the toolchain.
When I run "gcc-v"
I get a lot parameters like prefix, sysroot and more that show the directory it was build in:
/home/tal/buildroot/2014.08/...
Which leads me again to think that I'm doing something wrong...
Any help will be appreciated.
Thanks,
Tal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20141004/b0d48963/attachment.html>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] How to deploy Buildroot's crosscompile toolchain???
2014-10-05 6:32 [Buildroot] How to deploy Buildroot's crosscompile toolchain??? Tal Lubko
@ 2014-10-05 6:38 ` Waldemar Brodkorb
2014-10-05 8:07 ` Tal Lubko
2014-10-05 9:50 ` Peter Kuemmel
1 sibling, 1 reply; 6+ messages in thread
From: Waldemar Brodkorb @ 2014-10-05 6:38 UTC (permalink / raw)
To: buildroot
Hi,
Tal Lubko wrote,
> Hi
>
> I've wanted to ask what is the right way to build and deploy Buildroot's
> toolchain to other machines?
> These machines don't have Buildroot to build the toolchain.
>
> Currently (being ignorant about the right way to do it), after building the
> toolcahin, I'm just making a tar of output/host and copy it to other machine.
> There I'm untarring it to some directory and starting to cross compile...
>
> Things seemed to be working when I've worked with an External toolchain (
> Sourcery CodeBench). However when I've switched to Buildroot's toolchain, I got
> a message about missing libmpc.so.3. Then I've started to wonder what is the
> right way to build and deploy the toolchain.
>
> When I run "gcc -v"
> I get a lot parameters like prefix, sysroot and more that show the directory it
> was build in:
> /home/tal/buildroot/2014.08/...
>
> Which leads me again to think that I'm doing something wrong...
> Any help will be appreciated.
I am not 100% sure, but I think buildroot internal toolchains are
not relocatable. At least not via a relative sysroot directory.
best regards
Waldemar
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] How to deploy Buildroot's crosscompile toolchain???
2014-10-05 6:38 ` Waldemar Brodkorb
@ 2014-10-05 8:07 ` Tal Lubko
0 siblings, 0 replies; 6+ messages in thread
From: Tal Lubko @ 2014-10-05 8:07 UTC (permalink / raw)
To: buildroot
Hi Waldemar
Thanks for your help.
So, is there a recommendation as to how to deploy toolchain to other machines?
Tal
________________________________
From: Waldemar Brodkorb <wbx@openadk.org>
To: Tal Lubko <tallubko@yahoo.com>
Cc: "buildroot at busybox.net" <buildroot@busybox.net>
Sent: Sunday, October 5, 2014 9:38 AM
Subject: Re: [Buildroot] How to deploy Buildroot's crosscompile toolchain???
Hi,
Tal Lubko wrote,
> Hi
>
> I've wanted to ask what is the right way to build and deploy Buildroot's
> toolchain to other machines?
> These machines don't have Buildroot to build the toolchain.
>
> Currently (being ignorant about the right way to do it), after building the
> toolcahin, I'm just making a tar of output/host and copy it to other machine.
> There I'm untarring it to some directory and starting to cross compile...
>
> Things seemed to be working when I've worked with an External toolchain (
> Sourcery CodeBench). However when I've switched to Buildroot's toolchain, I got
> a message about missing libmpc.so.3. Then I've started to wonder what is the
> right way to build and deploy the toolchain.
>
> When I run "gcc -v"
> I get a lot parameters like prefix, sysroot and more that show the directory it
> was build in:
> /home/tal/buildroot/2014.08/...
>
> Which leads me again to think that I'm doing something wrong...
> Any help will be appreciated.
I am not 100% sure, but I think buildroot internal toolchains are
not relocatable. At least not via a relative sysroot directory.
best regards
Waldemar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20141005/b17b0449/attachment.html>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] How to deploy Buildroot's crosscompile toolchain???
2014-10-05 6:32 [Buildroot] How to deploy Buildroot's crosscompile toolchain??? Tal Lubko
2014-10-05 6:38 ` Waldemar Brodkorb
@ 2014-10-05 9:50 ` Peter Kuemmel
2014-10-05 12:35 ` Tal Lubko
1 sibling, 1 reply; 6+ messages in thread
From: Peter Kuemmel @ 2014-10-05 9:50 UTC (permalink / raw)
To: buildroot
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20141005/ce6417cf/attachment.html>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] How to deploy Buildroot's crosscompile toolchain???
2014-10-05 9:50 ` Peter Kuemmel
@ 2014-10-05 12:35 ` Tal Lubko
2014-10-05 14:25 ` Matthew Weber
0 siblings, 1 reply; 6+ messages in thread
From: Tal Lubko @ 2014-10-05 12:35 UTC (permalink / raw)
To: buildroot
Hi
For some reason with external toolchain it's different...
I've found out that the right way to do it is to set "Build options --> Host dir" to the desired path (/opt/<bla_bla>)
Thanks for the help
Tal
________________________________
From: Peter Kuemmel <syntheticpp@gmx.net>
To:
Cc: "buildroot at busybox.net" <buildroot@busybox.net>
Sent: Sunday, October 5, 2014 12:50 PM
Subject: Re: [Buildroot] How to deploy Buildroot's crosscompile toolchain???
Hi Tal,
when you change the "host dir" to a sharable path (something like /opt/buildroot/compiler")
then I assume you could copy this directory to another machine, at least when the Linux is the same.
I've not tested it, but the compiler in the "host dir" is usable even when I remove the output/ dir.
I use such a compiler as external toolchain for multiple buildroot configuration without having to
rebuild the compiler each time after a complete clean of the buildroot directory.
Only disadvantage is that you must make the subdirectory in /opt user-writable.
Peter
Gesendet: Sonntag, 05. Oktober 2014 um 08:32 Uhr
Von: "Tal Lubko" <tallubko@yahoo.com>
An: "buildroot at busybox.net" <buildroot@busybox.net>
Betreff: [Buildroot] How to deploy Buildroot's crosscompile toolchain???
Hi
I've wanted to ask what is the right way to build and deploy Buildroot's toolchain to other machines?
These machines don't have Buildroot to build the toolchain.
Currently (being ignorant about the right way to do it), after building the toolcahin, I'm just making a tar of output/host and copy it to other machine. There I'm untarring it to some directory and starting to cross compile...
Things seemed to be working when I've worked with an External toolchain (Sourcery CodeBench). However when I've switched to Buildroot's toolchain, I got a message about missing libmpc.so.3. Then I've started to wonder what is the right way to build and deploy the toolchain.
When I run "gcc-v"
I get a lot parameters like prefix, sysroot and more that show the directory it was build in:
/home/tal/buildroot/2014.08/...
Which leads me again to think that I'm doing something wrong...
Any help will be appreciated.
Thanks,
Tal
_______________________________________________ buildroot mailing list buildroot at busybox.net http://lists.busybox.net/mailman/listinfo/buildroot
_______________________________________________
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/20141005/ca4eea36/attachment.html>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] How to deploy Buildroot's crosscompile toolchain???
2014-10-05 12:35 ` Tal Lubko
@ 2014-10-05 14:25 ` Matthew Weber
0 siblings, 0 replies; 6+ messages in thread
From: Matthew Weber @ 2014-10-05 14:25 UTC (permalink / raw)
To: buildroot
Tal,
On Oct 5, 2014 7:35 AM, "Tal Lubko" <tallubko@yahoo.com> wrote:
>
> Hi
>
> For some reason with external toolchain it's different...
> I've found out that the right way to do it is to set "Build options -->
Host dir" to the desired path (/opt/<bla_bla>)
There is an open todo to make the buildroot toolchain relocatable. I think
this might have been discussed at a previous developers meeting (see
meeting notes from last year, i think...).
Beyond the compiler, there are also possible issues with absolute paths in
python scripts, .pc files for pkgconfig, or other scripts installed in the
host folder structure used as host tools. Personally we wrote a script to
handle installing of a sdk(host, legal info and images folders) release
which does the required fixups but still has a limitation of needing a
relocatable toolchain(so we test to make sure it is).
>
> Thanks for the help
> Tal
>
> ________________________________
> From: Peter Kuemmel <syntheticpp@gmx.net>
> To:
> Cc: "buildroot at busybox.net" <buildroot@busybox.net>
> Sent: Sunday, October 5, 2014 12:50 PM
> Subject: Re: [Buildroot] How to deploy Buildroot's crosscompile
toolchain???
>
> Hi Tal,
>
> when you change the "host dir" to a sharable path (something like
/opt/buildroot/compiler")
> then I assume you could copy this directory to another machine, at least
when the Linux is the same.
>
> I've not tested it, but the compiler in the "host dir" is usable even
when I remove the output/ dir.
> I use such a compiler as external toolchain for multiple buildroot
configuration without having to
> rebuild the compiler each time after a complete clean of the buildroot
directory.
>
> Only disadvantage is that you must make the subdirectory in /opt
user-writable.
>
> Peter
>
> Gesendet: Sonntag, 05. Oktober 2014 um 08:32 Uhr
> Von: "Tal Lubko" <tallubko@yahoo.com>
> An: "buildroot at busybox.net" <buildroot@busybox.net>
> Betreff: [Buildroot] How to deploy Buildroot's crosscompile toolchain???
>
>
> Hi
>
> I've wanted to ask what is the right way to build and deploy Buildroot's
toolchain to other machines?
> These machines don't have Buildroot to build the toolchain.
>
> Currently (being ignorant about the right way to do it), after building
the toolcahin, I'm just making a tar of output/host and copy it to
other machine. There I'm untarring it to some directory and starting to
cross compile...
>
> Things seemed to be working when I've worked with an External toolchain
(Sourcery CodeBench). However when I've switched to Buildroot's toolchain,
I got a message about missing libmpc.so.3. Then I've started to wonder what
is the right way to build and deploy the toolchain.
>
> When I run "gcc -v"
> I get a lot parameters like prefix, sysroot and more that show the
directory it was build in:
> /home/tal/buildroot/2014.08/...
>
> Which leads me again to think that I'm doing something wrong...
> Any help will be appreciated.
>
> Thanks,
> Tal
> _______________________________________________ buildroot mailing list
buildroot at busybox.net http://lists.busybox.net/mailman/listinfo/buildroot
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
>
>
> _______________________________________________
> 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/20141005/466191ff/attachment.html>
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-10-05 14:25 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-10-05 6:32 [Buildroot] How to deploy Buildroot's crosscompile toolchain??? Tal Lubko
2014-10-05 6:38 ` Waldemar Brodkorb
2014-10-05 8:07 ` Tal Lubko
2014-10-05 9:50 ` Peter Kuemmel
2014-10-05 12:35 ` Tal Lubko
2014-10-05 14:25 ` Matthew Weber
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox