Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Aleksandar Zivkovic <Aleksandar.Zivkovic@rt-rk.com>
To: buildroot@busybox.net
Subject: [Buildroot] Using Buildroot generated toolchain on different machine without Buildroot environment
Date: Thu, 28 Jun 2012 00:03:21 +0200	[thread overview]
Message-ID: <jsfvv6$6l2$1@dough.gmane.org> (raw)
In-Reply-To: <20120626175810.5725388e@skate>

On 26/06/2012 17:58, Thomas Petazzoni wrote:
> Le Tue, 26 Jun 2012 15:48:14 +0000 (UTC),
> Grant Edwards<grant.b.edwards@gmail.com>  a ?crit :
>
>> Toolchains built with crosstool-ng can be moved anywhere, but all you
>> end up with is the basic "libc" libraries.  You'll have to copy the
>> libraries built by buildroot manually if you want to use them on the
>> other hosts.
>
> Correct, but many things besides the toolchain contain hardcoded paths:
> the pkg-config binary, the external toolchain wrapper, the .la files,
> etc. See the report I mentioned for details.
>
> Thomas
Hi all,

@Thomas: when I used the same path on other machine build works 
correctly. Thanks again for quick response!

@Grant: I agree, besides libc I'm using complete generated host 
directory which holds other libraries that might be needed. Thanks for 
hint!

Regards,
Aleksandar

      reply	other threads:[~2012-06-27 22:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26 15:05 [Buildroot] Using Buildroot generated toolchain on different machine without Buildroot environment Aleksandar Zivkovic
2012-06-26 15:19 ` Thomas Petazzoni
2012-06-26 15:48   ` Grant Edwards
2012-06-26 15:58     ` Thomas Petazzoni
2012-06-27 22:03       ` Aleksandar Zivkovic [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='jsfvv6$6l2$1@dough.gmane.org' \
    --to=aleksandar.zivkovic@rt-rk.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox