All of lore.kernel.org
 help / color / mirror / Atom feed
From: sjhill at realitydiluted.com <sjhill@realitydiluted.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with buildroot and external toolchain
Date: Tue, 17 Jun 2008 13:38:41 -0500	[thread overview]
Message-ID: <20080617183841.GA18089@real.realitydiluted.com> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE1909182568@mi8nycmail19.Mi8.com>

> I think I worked the problem down to the external toolchain libraries
> not getting copied to the root filesystem. The copy_toolchain_lib_root
> in ext-tool.mk does locate the libraries to copy but I don't get the
> messages about the libraries being copied.
> 
> The only thing I can figure is the find in:
> 
> 	for FILE in `find $${LIB_DIR} -maxdepth 1 -type l -name
> "$${LIB}*"`; do { \
> 
> Is failing for some reason. Can anyone please offer any help on this?
> 
Here is what I have for an external glibc-based toolchain:

BR2_TOOLCHAIN_EXTERNAL_LIB_C="libc.so.6"
BR2_TOOLCHAIN_EXTERNAL_LIBS="ld.so.1 libcrypt.so libdl.so libgcc_s.so libm.so libnsl.so libnss_dns.so libnss_files.so libpthread.so libresolv.so librt.so libstdc++.so libutil.so"

BR2_TOOLCHAIN_EXTERNAL_PATH="/opt/toolchains/gcc-3.4.5-glibc-2.3.6/powerpc-7450-linux-gnu"
BR2_TOOLCHAIN_EXTERNAL_PREFIX="powerpc-7450-linux-gnu"

The libraries will be copied from:

  $(BR2_TOOLCHAIN_EXTERNAL_PATH)/$(BR2_TOOLCHAIN_EXTERNAL_PREFIX)/lib

Hope that helps.

-Steve

  reply	other threads:[~2008-06-17 18:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-17 17:41 [Buildroot] Problem with buildroot and external toolchain hartleys
2008-06-17 18:38 ` sjhill at realitydiluted.com [this message]
2008-06-17 18:57   ` hartleys
2008-06-17 19:04     ` Peter Korsgaard
2008-06-17 19:13       ` hartleys
2008-06-17 20:15       ` hartleys
2008-06-18  6:46         ` Peter Korsgaard
2008-06-18 18:28           ` hartleys

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=20080617183841.GA18089@real.realitydiluted.com \
    --to=sjhill@realitydiluted.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.